On Wed, Jan 18, 2012 at 02:44:34PM -0800, Brian Smith wrote: > Mike Hommey wrote: > > Please note that this is going to be a problem on systems that have > > system nspr and nss libraries that other system libraries use. > > I am intending to avoid changing how NSS is linked on Linux, at least at the > beginning. My priorities are are Android and Windows first, then Mac. > > In the long run, for performance reasons, we should probably prefer the > system NSS libraries to our own, whenever the system NSS libraries are > available and are the right version, because at least some of them are likely > to already have been loaded into RAM by other applications. It seems like > this may avoid the types of issues you are concerned about too.
Except if we change the current trend, which is to use unreleased nspr/nss code in mozilla, there's no way this can be sustainable. Mike -- dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
