Yea, that's the way I interpreted it, I just reiterated it unclearly.
That's the problem - I can't serialize the access to a single SSL - I need
two threads to access it, one blocking on an SSL_read and another issuing
SSL_write calls as data from an outside source becomes available for writing
across the SSL connection.
-----Original Message-----
From: Taral [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 27, 2000 2:46 PM
To: [EMAIL PROTECTED]
Subject: Re: Does anyone know how to fix Multithreading??
On 27 Jun, Lenny Foner wrote:
> 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
> [you mean, "nonblocking"?]
> 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.
No, he means that you should make a lock for each SSL structure, store
it in the ex_data member and write SSL_read and SSL_write wrappers that
claim/release that lock with each call. That way only concurrent
accesses to the _same_ SSL structure will be serialized.
Taral
______________________________________________________________________
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]
