From: Kurt D. Z. <Ku...@Op...> - 2000-05-10 14:16:55
|
At 02:48 PM 5/10/00 +0100, Graham Barr wrote: >That does not mean that Net::LDAP should not. Of course. >Whats the point of perl-ldap attempting to be as portable as >possible if there are servers, albeit broken servers, that it >cannot communicate with. The reality is that you will not be able to communicate with broken servers. Broken encoding will break all kinds of things. Yes, you can workaround this particular case, but this doesn't necessarily mean it's a good idea. You should consider the overall impact of such a change. Does the change effect client developers? Yes. If I have an array of outstanding requests which I grown by one for every new async message I send, my code will break when msgid generated jumps over 128. Does the change effect server admins? Yes. They will see msgid jump from 127 to 129 and will likely wonder what happen to 128. Now, one could argue that client developers and server admins shouldn't assume msgid increment by one for every new request. But the fact they general do is good for debugging as such oddities should be clues as to what's going wrong, not normal circumstance. |