aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2009-03-20 23:28:20 +0000
committerDaniel Stenberg <daniel@haxx.se>2009-03-20 23:28:20 +0000
commit31a7bfc47f2258f4825a7038d2f4e9f445a71cdf (patch)
tree321b6f6394b935111d9b6096d27f3c179b628eee
parent1b6d18fcb0539bfe1fa512f51f4b62cc326edb5b (diff)
Gary Maxwell helped us clarify that CURLOPT_SHARE specificly needs the locking
functions if the easy handles are used in multiple threads
-rw-r--r--docs/libcurl/curl_easy_setopt.35
1 files changed, 3 insertions, 2 deletions
diff --git a/docs/libcurl/curl_easy_setopt.3 b/docs/libcurl/curl_easy_setopt.3
index dd3473b99..9599b65e6 100644
--- a/docs/libcurl/curl_easy_setopt.3
+++ b/docs/libcurl/curl_easy_setopt.3
@@ -1726,8 +1726,9 @@ Pass a share handle as a parameter. The share handle must have been created by
a previous call to \fIcurl_share_init(3)\fP. Setting this option, will make
this curl handle use the data from the shared handle instead of keeping the
data to itself. This enables several curl handles to share data. If the curl
-handles are used simultaneously, you \fBMUST\fP use the locking methods in the
-share handle. See \fIcurl_share_setopt(3)\fP for details.
+handles are used simultaneously in multiple threads, you \fBMUST\fP use the
+locking methods in the share handle. See \fIcurl_share_setopt(3)\fP for
+details.
If you add a share that is set to share cookies, your easy handle will use
that cookie cache and get the cookie engine enabled. If you unshare an object