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

FAQ: expand the thread-safe section

Browse Source 
... with a mention of *NOSIGNAL, based on talk in bug #1386
This commit is contained in:
Daniel Stenberg 2014-07-09 22:06:34 -05:00
parent 1cef8f0bc3
commit 6273b23a05
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/FAQ
View File

@ -1099,6 +1099,12 @@ FAQ
your system has such. Note that you must never share the same handle in your system has such. Note that you must never share the same handle in
multiple threads. multiple threads.
libcurl's implementation of timeouts might use signals (depending on what it
was built to use for name resolving), and signal handling is generally not
thread-safe. Multi-threaded Applicationss that call libcurl from different
threads (on different handles) might want to use CURLOPT_NOSIGNAL, e.g.:
curl_easy_setopt(handle, CURLOPT_NOSIGNAL, true);
If you use a OpenSSL-powered libcurl in a multi-threaded environment, you If you use a OpenSSL-powered libcurl in a multi-threaded environment, you
need to provide one or two locking functions: need to provide one or two locking functions: