On Wed, 13 Dec 2006, Chris Nystrom wrote:
>> Nothing within libssh2 should ever hang waiting for network traffic in
>> either direction if the socket is set non-blocking.
>
> Yes, a blocking read was the only thing that worked for me, which was a
> problem, as my app is multi-threaded and I can
On 12/13/06, Daniel Stenberg <[EMAIL PROTECTED]> wrote:
>
> My goal with this whole non-blocking work is to allow an application to do
> poll() (or equivalent) on the socket and then have it call libssh2 that would
> deal with what it can deal with and return back without hanging waiting for
> furt
Hey
I'm now starting to get somewhere with my rewrite of some libssh2 internals to
start working in a non-blocking manner.
Currently, I have changed how libssh2_packet_read() works and it now returns a
libssh2packet_t type which can be:
- a positive number like before meaning packet type since
