On Wed, 21 Jul 2010, Íèêèòà Äîðîõèí wrote:

> > There are lots of function calls that are assumed to be rather fast and
> > won't be prematurely aborted with signals if they're not.

> Daniel, speaking of a bunch of functions you mentioned above, are these
> functions have to do with data transmission over the TCP socket connection?

Yes, and things like calls to the SSL library. But recall that we use
non-blocking sockets exclusively within libcurl so the regular
socket-functions should never ever take a very long time.

> If so, then if we lost Internet connectivity then these functions
> potentially may timeout after the timeout value which had been set with
> CURLOPT_TIMEOUT option. Is it correct?

No, when we lose connectivity we should still reach the timeout as we'd then
just loop waiting for input.

> One more question, who downloads the certificate from the HTTPS server,
> Libcurl or openssl?

OpenSSL does the heavy lifting, but some of the logic is done by libcurl. See
lib/ssluse.c for the OpenSSL-specific code.

-- 
  / daniel.haxx.se

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2010-07-21