On Sun, 22 Apr 2007, James Housley wrote:
> That and there is a long way/time to go until all the functions exist in
> both modes. In the mean time, if the current blocking state of the socket
> were detected and channel->blocking was set by then, existing programs
> should continue to work with the new versions of the library.
Sorry, but I'm not following.
I see two different ways to do the API
1) We have libssh2_channel_set_blocking() and it controls *ALL* functions to
do blocking or non-blocking. This didn't work before, and I didn't take
this route when I started to add *nb() functions.
2) We have a set of *nb() functions for non-blocking operations. Why the need
for libssh2_channel_set_blocking() then?
Are you saying you want libssh2_channel_set_blocking() to remain since we
don't yet have all the *nb() functions we want and that the function actually
make some of the non-*nb() functions non-blocking?
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
libssh2-devel mailing list
libssh2-devel_at_lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libssh2-devel
Received on 2007-04-22