aboutsummaryrefslogtreecommitdiff
path: root/docs/libcurl/libcurl-tutorial.3
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2014-09-19 12:54:19 +0200
committerDaniel Stenberg <daniel@haxx.se>2014-09-19 12:54:19 +0200
commit9d49e4706eb1b3d6a22ef1c129685525532ad695 (patch)
tree65deaaf75d73df592b0354b5717a17c5f21ee62f /docs/libcurl/libcurl-tutorial.3
parent17932a8f7b0168997f3e66491c760a99104ea381 (diff)
tutorial: signals aren't used for the threaded resolver
Diffstat (limited to 'docs/libcurl/libcurl-tutorial.3')
-rw-r--r--docs/libcurl/libcurl-tutorial.32
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/libcurl/libcurl-tutorial.3 b/docs/libcurl/libcurl-tutorial.3
index 11f2125f1..bc0921536 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