Re: Non-blocking SSLWrite problems
Re: Non-blocking SSLWrite problems
- Subject: Re: Non-blocking SSLWrite problems
- From: Frederick Cheung <email@hidden>
- Date: Wed, 12 Oct 2005 22:25:10 +0100
On 10/12/05, Brian Webster <email@hidden> wrote:
> On Oct 12, 2005, at 12:08 PM, Rich Siegel wrote:
>
> > As far as I know, the SSLWriteProc should never return
> > errSSLWouldBlock,
> > and in fact none of mine ever do. Your SSLWriteProc should push the
> > data
> > at the socket, set *dataLength to the actual amount of data that was
> > actually transmitted, and only return an error if you want the whole
> > process to abort.
> The way the docs are written implies that you should be able to
> return errSSLWouldBlock. From the discussion of the SSLWriteFunc
> callback:
>
I've certainly done this in my ssl write funcs without any problems.
I'm curious, after you have returned errSSLWouldBlock (and SSLWrite
has returned) does SecureTransport call your SSLWriteProc again with
the remainder of the data?
Fred
_______________________________________________
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