David, > > I assume this a reason why OpenSSL has the locking callback > functions. > > No. OpenSSL has the locking callback functions so it can > protect internal > structures. For example, if two SSL objects internally reference the > objects.
I am still confused as to why the locking callbacks would protect internal structures but not allow access of the SSL objects from different threads at the same time (i.e. SSL_read() and SSL_write()). > > As long as you use these it is safe to share the object AFAIK. > > Then when wouldn't it be safe to share the object? The > locking callback functions are required for all multithreaded applications or > else OpenSSL can't protect its internal state. Sorry. I'm not sure what you are saying here. Cheers, Mark. ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
