Subject: Re: proper use of non-blocking read

Re: proper use of non-blocking read

From: Peter Stuge <>
Date: Wed, 17 Apr 2013 00:45:47 +0200

Eric Frias wrote:
> On 4/10/2013 6:44 PM, Chris Hecker wrote:
> > the only real fix is an internal queue and changing EAGAIN
> > semantics slightly, as discussed in that thread.

I think that breaking backwards compatibility like that is an
absolute no-go.

Unless we can magically make old libssh2 users work reliably, we
can't change any semantics.

Instead, add new, non-broken, APIs and error codes, and make
transition as easy as possible.

> a multi-threaded app that could be doing file transfers in several threads

Basically you need to lock the session for the duration of each

Received on 2013-04-17