Hey I'm planning on committing what I have within a few days. It works for me with both by blocking and non-blocking tests, but I want to commit it to better allow more people to test and to proceed with my previously mention debug/log output change in a separate commit/change. I'll just do some further testing with curl (switched to using the non-blocking API) first.
I don't plan on breaking anything (except perhaps the API at previously mentioned places) but my changes go into the most lowlevel parts of the lib so it isn't totally unlikely that a bug or two find their ways in. I'll also continue and convert the SFTP directory listing to non-blocking after my initial commit. Oh, and I'm thinking I'll tag the CVS before my commit with a tag named "before-nonblocking" or similar to ease diffs etc between before and after. If anyone objects to this plan, please speak up. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ libssh2-devel mailing list libssh2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libssh2-devel
