As long as you are not using SSL, the only NSPR issues you should run into are memory management, threading, and shared library loading.
NSS only uses NSPR locking functions, it does not create any threads itself, so you only need implementations for PR_CreateThread, PR_Lock, PR_Unlock, nad PR_DestroyThread. Memory management is another matter. NSS uses NSPR's arena functions. These functions are in the NSPR 'service' library, not NSPR proper, and can be pulled out independent of NSPR itself. It also only depends on locking, and does not create threads, do IO, or load libraries. NSS's shared library loading is contained in pk11wrap for loading PKCS #11 modules. In addition there may be some NSPR defines that NSS depends on (like PRUInt32), but those should be relatively simple to identify and fix. bob bonny joy wrote: > hi friends > i am developing separate modules of pki.like pkcs7,pkcs5 etc > all these things should be independent with out any dependencies. > in mozilla we are using nss.which is implemented based on nspr. > can any one help me in this regard.that means avoiding nsprs thread > capabalities etc.i am not concerned with memory managemant or efficiency. > i mean i just want to take nss's logic but avoiding nsprs complexities. > thanks in advance > > > bonny > > _________________________________________________________________ > MSN Photos is the easiest way to share and print your photos: > http://photos.msn.com/support/worldwide.aspx > >
