Kurt D. Zeilenga wrote: >>I have been following this thread a bit. And while I would agree that >>the API (Net::LDAP in this case) should not do transcoding, I don't see >>any reason why it cannot provide hooks to make the application >>developers life easier. > >My point is that the application needs to be complete control of >transcoding as only its knows what needs to be transcoded, but I >note that providing enough context for the application to make the >right decision can be tricky. Of course you can limit the callbacks >to a few basic cases (such as attribute values associated with >attribute descriptions), but more complete solutions get ugly >pretty fast.
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. Dan
