Daniel Stenberg schrieb:
> Yes. If they return NULL you must use libssh2_session_last_error() to
> check
> the reason for it.
>
Thank you very much for your help!
Marcus
--
Register Now & Save for Velocity, the Web P
On Tue, 28 Apr 2009, double wrote:
> Thanks again for your detailed explanation. For functions like
> "libssh2_channel_open_ex()" or "libssh2_sftp_open_ex()" I must check
> "libssh2_session_last_error()" in order to get EAGAIN?
Yes. If they return NULL you must use libssh2_session_last_error()
Daniel Stenberg schrieb:
> First: LIBSSH2_ERROR_EAGAIN is a return code lots of libssh2 functions
> can
> return when used in non-blocking mode.
> ...
> But yes, the list of functions that may return EAGAIN (or in some cases NULL
> due to an EAGAIN situation) is this:
>
Hi Daniel,
Thanks ag
On Tue, 28 Apr 2009, double wrote:
> I am re-writing my code using non-blocking sockets. The demos check the
> returncode for "LIBSSH2_ERROR_EAGAIN", but most of the libssh2 functions use
> the "BLOCK_ADJUST()" macro.
Let's not mix apples and oranges here.
Hello,
I am re-writing my code using non-blocking sockets. The demos
check the returncode for "LIBSSH2_ERROR_EAGAIN", but most
of the libssh2 functions use the "BLOCK_ADJUST()" macro.
Is it still necessary to check the returncode for EAGAIN? If yes,
is there a list of dangero
