.
Cheers.
--Yunhong
-Original Message-
From: Nicolas Roumiantzeff [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 20, 1999 4:18 AM
To: [EMAIL PROTECTED]
Cc: "Sean O'Dell"@epsilon.engelschall.com
Subject: Re: Non-blocking I/O help
For me, it works only for SSL_read and
On Mon, Dec 20, 1999 at 01:18:04PM +0100, Nicolas Roumiantzeff wrote:
> As SSL_connect and SSL_accept make several calls to the underlying socket
> API, the SSL_ERROR_WANT_READ failure can happen in the middle of the
> processing, not just on the first read, so calling it later wont work
> becau
PROTECTED]>
À : List: <[EMAIL PROTECTED]>
Cc : "Sean O'Dell"@epsilon.engelschall.com <"Sean
O'Dell"@epsilon.engelschall.com>
Date : samedi 18 décembre 1999 22:12
Objet : Re: Non-blocking I/O help
>Sean O'Dell <[EMAIL PROTECTED]> in ulf.
Sean O'Dell <[EMAIL PROTECTED]> in ulf.openssl.users:
>[...] SSL_connect, SSL_accept, SSL_read and SSL_write. Apparently, when the
> underlying socket is in non-blocking mode, these functions can/may/tend to
> behave in a non-blocking way also. What I'd like to know is, how can I tell
> when th
