Rob Crittenden wrote:
b) do all the work on the first module load. Don't really shut down the
module after the first load (that is, pretend that you shut down).
Then do nothing on the second load, and continue to use the stuff
loaded
the first time.
I don't have the choice with b). Apache forcibly unloads the module
(dlcose()). If I haven't shut things down right I'll get a
SEC_ERROR_BUSY error during subsequent reloads.
Actually, you can do b by doing an extra dlopen() in your module's own
shared library when it gets initialized. This will cause the refcount on
your module to go up. So, the dlclose() in Apache will have no effect.
This is essentially leaking the module, but it solves the problem very well.
_______________________________________________
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-crypto
