----- Original Message ----- From: "David Schwartz" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, January 06, 2004 11:39 AM Subject: RE: OpenSSL: threading question
> > > [I suspect (based on the all-caps spelling of SOCKET and the sample > > code provided earlier) that Mr. Giudicelli speaks from a Windows > > perspective, which doesn't handle multiple processes very well, and > > certainly does not abstract tcp sockets into simple file descriptors > > the way unix does.] > > The irony is that on Windows, with IOCP, it's even more common to have > concurrent reads and writes to the same socket handled by different threads. > IOCP throws read and write events into the same event queue because you > associate a socket with a completion port! IOCP ? Are you talking about WinSock2 ? The WSA* functions ? I should remind that the technical problem was never really, read and write from 2 threads, but more read and read from 2 threads (SSL_read and SSL_write). All I said was, "since you will only have one access to the socket, I see no points having two threads". Personally I would have one thread that picks from both queues, that would save resources. This is just a personnal programation view. No debate needed over this. Fred. ______________________________________________________________________ > 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]
