At 01:11 AM 8/15/2003, Dan Oscarsson wrote: >As I have written my additions to perl-ldap the user supplies >translation routines between "local" and protocol character set. >And they are used to translate DNs and values for attribute descriptions >that are not binary. One could probably easy extend my code so that >the user could define what attribute descriptions should be >translated. The code does just what I would have to do before calling >the API, if I had not added the code to the perl-ldap code. >It might not be enough for very complex cases, but in that case >you do not need to enable translation. It should be enough for a large >amount of applications.
This is basically what U-Mich LDAP had in their LDAP C API. It was found to be generally inadequate as it did provide the application with enough control over when, where, and how the translation was to be done. The feature caused far more problems than it ever resolved. Even where applications tried to limit the set of attributes to those using one encoding, the feature was found to be problematic. In particular, the feature never dealt with escaping in character string encodings (such as in DN strings). Things are not as simple as they seem. Have fun. Kurt
