On Sun, Mar 20, 2011, Victor Duchovni wrote: > once, ... so there needs to be some once-only code in your application,
That's trivial to do and already working fine. > and setting a write-once global there does not seem burdensome. As Graham points out it makes it hard for some applications to use multiple contexts. In my case I have libraries that implement server side and client side, and I want to be able to run them in separate processes or in a common process. In the latter case having global variables makes the implementation more complex than it should be. > I am not aware of any other mechanism for passing application context > into the session callback routines. Thanks for the information! So I'll either have to find a way to implement this without callbacks (might not be possible...) or use some dirty tricks to deal with the global variables that OpenSSL's API requires. ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
