Out of curiosity, doesn't one also have to lock the SSL* itself against concurrent access during read/write operations, or does OpenSSL guard it for the programmer?
thanks, jerry -----Original Message----- From: Sankaran Narayanan [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 27, 2001 10:44 AM To: [EMAIL PROTECTED] Subject: RE: Question on SSL_dup... > I am afraid that SSL_dup() does not fulfill your requirements. > You can only have one datastream through one SSL object at a time, > so that you cannot have two threads concurrently accessing one SSL object. Thanks. It was fairly trivial to write a "reference counted" wrapper object for SSL*, so that i could avoid using SSL_dup and still allow multiple threads to do free. thanks anyway. ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED] ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
