> In fact I'm using a custom BIO to interface between OpenSSL and some
> custom buffer structures. If I hadn't misread the protocol, for
> application data, SSL_write() should be able to proceed even when a
> SSL_read() returned WANT_READ. But what about rehandshake? If the
> SSL_read() returned W
> When using nonblocking BIO, can SSL_write(ssl, ...) be called right
> after a SSL_read(ssl, ...) "returned" SSL_ERROR_WANT_READ/WRITE? Or vice
> versa, please?
Of course. You can attempt to send or receive any time you want to.
DS
_
On Mon, 15 May 2006 22:07:17 -0400 (EDT), "Mikhail Kruk"
<[EMAIL PROTECTED]> said:
> Assuming that we are talking about a regular tcp non-blocking socket, the
> answer is yes. SSL_read() is just telling you that your request can't be
> satisfied at the moment and should be retried after more da
On Tue, 16 May 2006, Wei Li wrote:
On Mon, 15 May 2006 21:40:22 -0400 (EDT), "Mikhail Kruk"
<[EMAIL PROTECTED]> said:
When using nonblocking BIO, can SSL_write(ssl, ...) be called right
after a SSL_read(ssl, ...) "returned" SSL_ERROR_WANT_READ/WRITE? Or vice
versa, please?
Always assume that
On Mon, 15 May 2006 21:40:22 -0400 (EDT), "Mikhail Kruk"
<[EMAIL PROTECTED]> said:
> > When using nonblocking BIO, can SSL_write(ssl, ...) be called right
> > after a SSL_read(ssl, ...) "returned" SSL_ERROR_WANT_READ/WRITE? Or vice
> > versa, please?
>
> Always assume that a non-blocking SSL_read a
Always assume that a non-blocking SSL_read and SSL_write can return both
WANT_READ and WANT_WRITE. It's not as difficult as they want you to
think.
When using nonblocking BIO, can SSL_write(ssl, ...) be called right
after a SSL_read(ssl, ...) "returned" SSL_ERROR_WANT_READ/WRITE? Or vice
vers
When using nonblocking BIO, can SSL_write(ssl, ...) be called right
after a SSL_read(ssl, ...) "returned" SSL_ERROR_WANT_READ/WRITE? Or vice
versa, please?
Thanks.
--
Regards,
Wei
--
http://www.fastmail.fm - Send your email first class
__
