Hi Eric, On Sunday, 3. December 2006 00:40, Eric Nichols wrote: > Ok I think I just answered my own question. Once I looked at the code it's > was pretty simple to patch in a change to make all this happen. > > So it now shows a combined output: > range-lower 1 > name sn > oid 2.5.4.4 > property-guid 417A96BFE60DD011A28500AA003049E2 > range-upper 64 > indexed 1 > property-set-guid 54018DE4F8BCD111870200C04FB96050 > aliases > type at > > The code is very non-invasive and is only a couple of lines. Can you > please add this to your package?
I cannot see any of the standard information in the example given above (such as description, matching rules, or syntax). The the patch you provide simply overrides the standard behaviour in favour of Microsoft's non-standard behaviour. (try to print the values of the %type2attr hash before and after your extension) I consider this patch not O.K. to be incorporated into Net::LDAP as it breaks compatibility with all other LDAP servers out there that adhere to the standard instead of inventing something different they then call LDAP. BTW the standard allows for vendor specific extension to be included into the attributeType or objectClass attributes - fields that start with "X-". So there was no need to create a non-standard extension on a separate attribute. Peter -- Peter Marschall [EMAIL PROTECTED]
