[libssh2] EAGAIN but waiting for what?

2008-07-03 Thread Daniel Stenberg
Hey I'm pondering about fixing one of the biggest flaws we have in libcurl's use of libssh2 for SCP and SFTP transfers, but in order to do this in a non-hackish way I think I need to modify the libssh2 API and I thought I'd ask for some general advice here. We use libssh2 entirely non-blocking

Re: [libssh2] EAGAIN but waiting for what?

2008-07-03 Thread Daniel Stenberg
On Thu, 3 Jul 2008, J.T. Conklin wrote: > FWIW, Just yesterday I learned that OpenSSL operations return either > SSL_ERROR_WANT_READ or SSL_ERROR_WANT_WRITE with a non-blocking BIO. This > seems better to me than having the library return an error code indicating > that the operation must be re

[libssh2] How to Compile libssh2 and exemples under windows ?

2008-07-03 Thread DAO Anh-Viet
Dear Sirs, I am trying to compile the new libcurl version 7.18.1 and libssh2 version 0.18 in order to user the protocol SFTP under Windows. But I meet the problem of lacking the include file, for example while compiling libssh2 version 0.18, I must de-active many Included file, such as: /* u

Re: [libssh2] Key Re-Exchange Patch

2008-07-03 Thread Daniel Stenberg
On Thu, 26 Jun 2008, Sean Peterson wrote: > I've remade the patches in the 'diff -u' format. Thanks, this has now been applied! -- / daniel.haxx.se - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Stud

Re: [libssh2] How to Compile libssh2 and exemples under windows ?

2008-07-03 Thread Neil Gierman
What I did is copy win32\libssh2_config.h to src\libssh2_config.h and that took care of all of my issues for both VS2005 and VS2008. Not tried with VC6 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of DAO Anh-Viet Sent: Thursday, July 03, 2008 11:15 AM To:

Re: [libssh2] EAGAIN but waiting for what?

2008-07-03 Thread J.T. Conklin
Daniel Stenberg <[EMAIL PROTECTED]> writes: > We use libssh2 entirely non-blocking as we can have N number of > simultanoues transfers in the same single thread. When > LIBSSH2_EAGAIN is returned we go back and wait for action on the > socket and then we call the same function again when action has