I am in the process of update libssh2_sftp_readdir() so it will work in true non-blocking mode, just like Daniel Stenberg did with his excellent work with libssh2_sftp_readnb() and libssh2_sftp_writenb (). However, I have noticed that now libssh2_sftp_read() and libssh2_sftp_write() explicitly set blocking to on in their operation, and I am guessing the same is true for libssh2_channel_read_ex() and libssh2_channel_write_ex(). While it always has been possible for the consumer of libssh2 to call libssh2_channel_set_blocking() and turn off blocking, did it work?
If it does work, are there programs that are depending on that functionality? The fix looks like it might be straight forward, just not force blocking on. If it doesn't work, should it be dropped from the external interface. Jim -- /"\ ASCII Ribbon Campaign . \ / - NO HTML/RTF in e-mail . X - NO Word docs in e-mail . / \ ----------------------------------------------------------------- [EMAIL PROTECTED] http://www.FreeBSD.org The Power to Serve [EMAIL PROTECTED] http://www.TheHousleys.net --------------------------------------------------------------------- "Eagles may soar, but weasels don't get sucked into jet engines" -- Anon ------------------------------------------------------------------------- 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libssh2-devel
