How to compile libcurl.so with libssh2 and openssl by VC8

2012-06-15 Thread 黄心怡
hi, I am trying to compile libcurl.so by VC8 with libssh2 and openssl, in order to support both SFTP and HTTPS. My libcurl version is 7.21.3 . When I look at the src/lib/Makfile.vc8, I find there is only option in CFG about ZLIB and SSL, but no LIBSSH2 found. So I search the web, and

Re: Thread safety

2012-06-15 Thread Daniel Stenberg
On Thu, 14 Jun 2012, Konstantin Miller wrote: Do you mean that although an explicit call to curl_global_init is not thread safe, an implicit call from, e.g., curl_easy_init is still thread safe? So that in a multi-threaded process I would not want to explicitely call curl_global_init but

Re: further schannel improvements

2012-06-15 Thread Yang Tse
Salisbury, Mark mark.salisb...@hp.com wrote: [...] I think I've incorporated all suggestions. These patches should be a little easier to read; after rebasing some of the things I was doing have been done already. I've just pushed the 0001-* one with some adjustments. Most notably I've

Re: SMTP recipient issues

2012-06-15 Thread Dan
On 6/8/2012 4:57 PM, Steve Holme wrote: Hiya, On Fri, 8 Jun 2012, Daniel Stenberg wrote: Alternatively if Daniel does mind us adding new SMTP specific error codes we could add CURLE_SMTP_MAIL_ERROR and CURLE_SMTP_RCPT_ERROR and change the data failed to be CURLE_SEND_ERROR. Did we come to

Re: further schannel improvements

2012-06-15 Thread Yang Tse
Yang Tse yangs...@gmail.com wrote: This commit alone doesn't provide yet all the WinCE stuff but should nicely prepare code base for it while hopefully not breaking anything. Yep, broken. Follow-up patch pushed. -- -=[Yang]=-

RE: SMTP recipient issues

2012-06-15 Thread Steve Holme
Hi Dan, Alternatively if Daniel does mind us adding new SMTP specific error codes we could add CURLE_SMTP_MAIL_ERROR and CURLE_SMTP_RCPT_ERROR and change the data failed to be CURLE_SEND_ERROR. Did we come to any sort of consensus about what the implementation should look like? I

Re: SMTP recipient issues

2012-06-15 Thread Dan
If you're referring to the if(smtpcode/100 != 2) then I would agree that it is a broad net to catch a small fish, however, it is more efficient to do this than have various if/else statements or a switch statement for the possible error codes that might come back from the server. At the end of

RE: SMTP recipient issues

2012-06-15 Thread Steve Holme
Hi Dan, If the response from the server is guaranteed to be 550 then we could do if(smtpcode != 550) but I'm not sure if that is the case / nor was Daniel when he originally wrote the function. Since most of the code is broken down into the specific parts, wouldn't it be fairly