Richard,

Thanks for the reply.

If I understand you correctly, you are suggesting that I put wrappers around
SSL_write and SSL_read that make them exclusive operations.  This
effectively makes the thing single-threaded again.  I need to have blocking
Reads in effect all the time on one thread while I'm writing on another.  I
can't very well single-thread the reads and writes.

Any other ideas?

Thanks again,

Bill Rebey


-----Original Message-----
From:   Richard Levitte - VMS Whacker [mailto:[EMAIL PROTECTED]]
Sent:   Tuesday, June 27, 2000 1:20 PM
To:     [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject:        RE: Does anyone know how to fix Multithreading??

From: "Erik" <[EMAIL PROTECTED]>

nolke> Do these thread problems also occur when sharing the same SSL
nolke> context but not the same SSL object?

No.  The SSL_CTX structure basically acts as a template for the SSL
structures you create, so they don't really carry any semantics that
are thread-sensitive.  At least, that's how I understand it.

-- 
Richard Levitte   \ Spannvägen 38, II \ [EMAIL PROTECTED]
Chairman@Stacken   \ S-168 35  BROMMA  \ T: +46-8-26 52 47
Redakteur@Stacken   \      SWEDEN       \ or +46-709-50 36 10
Procurator Odiosus Ex Infernis             -- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/
Software Engineer, Celo Communications: http://www.celocom.com/

Unsolicited commercial email is subject to an archival fee of $400.
See <http://www.stacken.kth.se/~levitte/mail/> for more info.
______________________________________________________________________
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]

Reply via email to