Dan Mosedale wrote:

> "Nelson B. Bolyard" ?[EMAIL PROTECTED]? writes:
> ? Dan Mosedale wrote:
> ?
> ? ? So one thing that would be helpful to those of us working on LDAP in
> ? ? the browser is the ability to get access to some of the NSS
> ? ? functionality for the LDAP C SDK to use.
> ? ?
> ? ? LDAP in the browser consists of an XPCOM wrapper around the LDAP C
> ? ? SDK, which does all the connection management for us under the hood.
> ? ? The C SDK itself uses raw or NSPR sockets to do all the work, and I'm
> ? ? told that the most recent version interacts with NSS 3.2 directly.
> ?
> ? ? Since we want to share as much code as possible, it would be really
> ? ? good not to have to link the C SDK against a second copy of NSS
> ? ? separate from PSM.  So in some ideal world, it seems like the LDAP
> ? ? XPCOM wrapper would be able to ask PSM for some set of raw function
> ? ? pointers to NSS functions which could then be passed into the LDAP C
> ? ? SDK for use.
> ? ?
> ? ? Comments?
> ?
> ? The LDAP C sdk has always used NSS.  In the past, it actually linked its
> ? own copy of NSS into its DSO/DLL.  Now, in NSS 3.2, it will simply use the
> ? NSS DSO, and no longer have its own copy.
> ?
> ? The LDAP C SDK developer is one of NSS's main Beta testers.
>
> One of the interesting pieces here, as I understand it, is that PSM
> doesn't use the NSS DSO; it statically links NSS because of an issue
> related to the symbols that NSS exports.  So we'd have to ship two
> copies of NSS with mozilla, which sort of defeats the code-sharing....

Also NSS does not always react well to multiple copies running at the same time.
This is one of the primary reasons PSM is out of process.

bob

>
>
> Dan


Reply via email to