Re: CURLE_GOT_NOTHING on slow connections
Date: Fri, 27 Feb 2004 21:55:19 +0100 (CET)
On Fri, 27 Feb 2004, Richard Bramante wrote:
> The real problem is the inability to implement a working verifyconnect() on
> Windows. If we had a working verifyconnect(), the select() issue is moot.
> I've tried several different approaches here, none of which have been
> successful. I suppose others have already gone through this exercise and
> failed, hence the #ifdef and just punting and returning TRUE.
There are two reasons we removed that code for Windows:
1. The win docs doesn't seem to mention the need for that verification.
2. It is a major performance hog when libcurl is used multi-threaded. There is
something very strange in there, but it sucks almost all CPU when you use
libcurl in 50 threads or so. (On windows that is).
-- Daniel Stenberg -- http://curl.haxx.se/ -- http://daniel.haxx.se/ [[ Do not send mails to this email address. They won't reach me. ]]Received on 2004-02-27