Re: SSLRead() causes SSLWriteFunc to be called?
Re: SSLRead() causes SSLWriteFunc to be called?
- Subject: Re: SSLRead() causes SSLWriteFunc to be called?
- From: Frederick Cheung <email@hidden>
- Date: Thu, 6 Oct 2005 20:40:59 +0100
While you can definitely use SecureTransport in a multithreaded
worlds, accessing the same SSLContext from more than one thread is
probably not a good idea.
Fred
On 10/6/05, David Francis <email@hidden> wrote:
> I am just beginning to work with the Secure Transport APIs. I have a
> setup which has a BSD socket opened and the SSLHandshake() on the
> main thread thread. Once the initial handshake is complete, I start
> a 2nd thread to read() the incoming bytes from the server. This 2nd
> thread basically blocks until some incoming data is available from
> the server.
>
> Strangely, when my 2nd thread calls SSLRead() my SSLWriteFunc
> callback is being hit. I have a breakpoint in my SSLWriteFunc and
> the stack trace shows that only SSLRead() is being called on the 2nd
> thread.
>
> Am I doing something wrong? How are people using Secure Transport in
> a multi-threaded environment?
>
> Thanks,
>
> David Francis
> President
> Francis Technical Services, LLC
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Macnetworkprog mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden