On Fri, Sep 27, 2002 at 09:57:15AM -0700, Cory Albrecht wrote:
> --- Lutz Jaenicke <[EMAIL PROTECTED]> wrote:
> > On Thu, Sep 26, 2002 at 11:36:36PM -0700, Cory Albrecht wrote:
> > > With buffer sizes of 8193 bytes or more, after SSL_write() returns
> > an
> > > error it NEVER succedes ever again
--- Lutz Jaenicke <[EMAIL PROTECTED]> wrote:
> On Thu, Sep 26, 2002 at 11:36:36PM -0700, Cory Albrecht wrote:
> > With buffer sizes of 8193 bytes or more, after SSL_write() returns
> an
> > error it NEVER succedes ever again on that socket. My program does
> it's
> > something else tasks, trying a
On Thu, Sep 26, 2002 at 11:36:36PM -0700, Cory Albrecht wrote:
> --- Xperex Tim <[EMAIL PROTECTED]> wrote:
> > Personally, I don't consider SSL_ERROR_WANT_WRITE to be an error. If
> > you are going to use
> > non-blocking sockets then you are going to have to expect that
> > sometimes the socket
--- Xperex Tim <[EMAIL PROTECTED]> wrote:
> Personally, I don't consider SSL_ERROR_WANT_WRITE to be an error. If
> you are going to use
> non-blocking sockets then you are going to have to expect that
> sometimes the socket won't be ready
> for writing. OpenSSL doen't want to busy-wait in that c
Personally, I don't consider SSL_ERROR_WANT_WRITE to be an error. If you are going to
use
non-blocking sockets then you are going to have to expect that sometimes the socket
won't be ready
for writing. OpenSSL doen't want to busy-wait in that case so it returns to you so
you can do
something
