From: Daniel Stenberg Date: Fri, 19 Sep 2014 10:54:19 +0000 (+0200) Subject: tutorial: signals aren't used for the threaded resolver X-Git-Tag: curl-7_39_0~209 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=9d49e4706eb1b3d6a22ef1c129685525532ad695;p=thirdparty%2Fcurl.git tutorial: signals aren't used for the threaded resolver --- diff --git a/docs/libcurl/libcurl-tutorial.3 b/docs/libcurl/libcurl-tutorial.3 index 11f2125f16..bc09215369 100644 --- a/docs/libcurl/libcurl-tutorial.3 +++ b/docs/libcurl/libcurl-tutorial.3 @@ -257,7 +257,7 @@ than one thread at any given time. libcurl is completely thread safe, except for two issues: signals and SSL/TLS handlers. Signals are used for timing out name resolves (during DNS lookup) - -when built without c-ares support and not on Windows. +when built without using either the c-ares or threaded resolver backends. If you are accessing HTTPS or FTPS URLs in a multi-threaded manner, you are then of course using the underlying SSL library multi-threaded and those libs