David Durkee wrote:
> Dear Csaba, Dan and Kevin,
>
> IMHO you will probably find the following link helpful:
> http://docs.iplanet.com/docs/manuals/communicator/ldap45.htm
Hey, someone actually reads that stuff. Cool!
> ) Which leads to the second issue, which I think is that at least in
> Netscape there are many "default" settings that can be changed in the
> pref.js file if a new setting is specified. BUT they do not need to be
> specified because they are "obviously" default. (you must love
> self-documenting code)
This is a pretty important point. As you can see in the doc above, the
4.x LDAP preferences have a *ton* of different settings which can be
specified in the prefs infrastructure (netscape.cfg, all.js, prefs.js).
The LDAP prefs C code (libmisc/dirprefs.c) goes to great length to avoid
dumping default values into the prefs.js file, which would bloat the
file considerably, making it harder to read and slower to parse.
Of course, the compiled-in prefs files make it easy to avoid putting
default values in the prefs file *if* you know the name of the pref at
compile-time, but since the LDAP pref names are dynamically generated,
we had all that yucky C code to do the same thing.
I think alecf and/or sspitzer solved that problem in a parallel way for
mail/news accounts in mozilla (although I do see some bloat in my prefs
file).
-- Phil. (LDAP alumnus scanning the group at dmose's request)
