Re: SSLWrite and SSLRead mutually exclusive?
Re: SSLWrite and SSLRead mutually exclusive?
- Subject: Re: SSLWrite and SSLRead mutually exclusive?
- From: Doug Mitchell <email@hidden>
- Date: Thu, 2 Oct 2003 07:40:02 -0700
A given SSLContextRef can only be used by one thread at any given time.
(The SecureTransport library as a whole is thread safe and reentrant;
this restriction just applies to an SSLContextRef).
Typically, applications which need more concurrency than this would
appear to provide will configure the I/O to be nonblocking.
--dpm
On Wednesday, October 1, 2003, at 08:07 PM, Larry Gerndt wrote:
(I'm writing an SSL client). In my non-SSL class, I have a send
thread and
a receive thread (these are MPTasks). The network I/O is done using
blocking sockets. I can write anytime I want, and when the receive
task
gets something, it notifies me. This results in really good
performance.
However, in my SSL class, which is using sockets as the underlying
transport, it appears that I cannot call SSLWrite while SSLRead is in
progress. This really bogs things down because now I have to first do
a
single write, then wait for the response. Is there way of overcoming
this
problem?
--
Larry Gerndt
AIM Handle: SonOfTheSonOfMan
Let the truth be told though the heavens fall -- James Garrison
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.