3 ms·
when i had to work with it the problem was incompatible implementations and extensions. i assume it would work fine with MS server and client, or with Sun (bac
by andrewcooke 14y ago
when i had to work with it the problem was incompatible implementations and extensions. i assume it would work fine with MS server and client, or with Sun (back then) server and client, but when you mixed them and tried to do anything even vaguely unusual, it hurt.
- lusr 14y agoI've had my .NET clients talk successfully to .NET back-ends, Java back-ends, and Cobol wrappers with no problems, with security extensions, etc. all enabled. But the key to that was having an active architecture group responsible for ensuring consistency across the organisation (libraries for each client platform host).