From: Graham B. <gb...@po...> - 2000-05-10 13:50:36
|
On Wed, May 10, 2000 at 06:42:41AM -0700, Kurt D. Zeilenga wrote: > At 02:20 PM 5/10/00 +0100, Graham Barr wrote: > >Ah, but it is a return of the value I send. So just avoid values where > >value & 0x80808080 is non-zero > > You could do something like: > msgid += msgid & 0x80808080; no that would not work, consider if msgid contained 0x7f80 > But I wouldn't as this won't fix all the other hosed encodings. True. > I prefer to get Microsoft to properly fix their products. So would I, but how long do you think that would take. > This > can be done through interoperability/certification testing programs. > I'll make a point of adding appropriate tests to the Basic > Interoperability Test Suite (BLITS). > > http://www.opengroup.org/directory/mats/blits23/blits23.htm > > Also, note, that I know of no LDAP SDK which attempts to workaround > such issues. That does not mean that Net::LDAP should not. 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. Graham. |