generic-library/curl
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Gary Maxwell helped us clarify that CURLOPT_SHARE specificly needs the locking

Browse Source 
functions if the easy handles are used in multiple threads
This commit is contained in:
Daniel Stenberg 2009-03-20 23:28:20 +00:00
parent 1b6d18fcb0
commit 31a7bfc47f
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/libcurl/curl_easy_setopt.3
View File

@ -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 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 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 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 handles are used simultaneously in multiple threads, you \fBMUST\fP use the
share handle. See \fIcurl_share_setopt(3)\fP for details. 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 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 that cookie cache and get the cookie engine enabled. If you unshare an object