Hi, I have an application where I create a TCP connection from the main thread and then spawn two seperate threads to do recv and send parallely. But, as I understand currently I just cannot switch to SSL in the same model. i.e I cannot do SSL_read from one thread and SSL_write from another thread on the same SSL connection (using the same SSL_S) without providing some application level mutex.
I have the following questions: (a) Does OpenSSL plan to support this feature in any of it's future releases? (Or does any of the releases already support it? I went through the Change Logs, but couldn't find anything), If no, why not? (b) As far as I understand, the main problem with the parallel SSL_read / SSL_write is renegotiation, i.e. a call to SSL_read can lead to a send call and vice-versa, so, if I ensure I don't do renegotiation at all (both sides use my application) then will the code work fine? (c) I would also like to know the reason behind such a design considering the fact that TCP supports parallel send / recv. Is it enforced by the protocol design or any other design parameters forced such a design? Expecting a reply! Thanks in Advance. Regards, Jay ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [email protected] Automated List Manager [email protected]
