At 01:20 AM 5/8/01 +0200, Lutz wrote:
>On Mon, May 07, 2001 at 04:25:10PM -0400, Tom Biggs wrote:
> > Say an application uses SSL_write() to write out (on a non-blocking socket)
> > a large buffer, which contains more bytes than an underlying SSL record
> can
> > carry.
> > What is the behavior i
Lutz Jaenicke <[EMAIL PROTECTED]> writes:
> On Mon, May 07, 2001 at 04:25:10PM -0400, Tom Biggs wrote:
> > Say an application uses SSL_write() to write out (on a non-blocking socket)
> > a large buffer, which contains more bytes than an underlying SSL record can
> > carry.
> > What is the behavi
On Mon, May 07, 2001 at 04:25:10PM -0400, Tom Biggs wrote:
> Say an application uses SSL_write() to write out (on a non-blocking socket)
> a large buffer, which contains more bytes than an underlying SSL record can
> carry.
> What is the behavior if, for example, one SSL record is successfully wr
5 PM
To: [EMAIL PROTECTED]
Subject: some questions on non-blocking SSL_write()
Say an application uses SSL_write() to write out (on a non-blocking socket)
a large buffer, which contains more bytes than an underlying SSL record can
carry.
What is the behavior if, for example, one SSL record
Say an application uses SSL_write() to write out (on a non-blocking socket)
a large buffer, which contains more bytes than an underlying SSL record can
carry.
What is the behavior if, for example, one SSL record is successfully written,
but EWOULDBLOCK is returned when OpenSSL tries to write th
