diff options
| author | Daniel Stenberg <daniel@haxx.se> | 2020-08-11 15:43:42 +0200 |
|---|---|---|
| committer | Daniel Stenberg <daniel@haxx.se> | 2020-08-11 15:43:42 +0200 |
| commit | 4bf5c4dc5d90f8d34b2161b9ad507df37ec5998a (patch) | |
| tree | d6522389184cb249fabd2b30210a5086a20a8197 /docs/libcurl/curl_share_setopt.3 | |
| parent | d4ea401966a90044b4d00e3d94eee84adb9fab43 (diff) | |
| download | curl-bagder/shared-conncache-threaded.tar.gz | |
KNOWN_BUGS: A shared connection cache is not thread-safebagder/shared-conncache-threaded
Closes #4915
Diffstat (limited to 'docs/libcurl/curl_share_setopt.3')
| -rw-r--r-- | docs/libcurl/curl_share_setopt.3 | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/libcurl/curl_share_setopt.3 b/docs/libcurl/curl_share_setopt.3 index 0291d93c2..7a3e2388c 100644 --- a/docs/libcurl/curl_share_setopt.3 +++ b/docs/libcurl/curl_share_setopt.3 @@ -74,10 +74,10 @@ by default. Note this symbol was added in 7.10.3 but was not implemented until 7.23.0. .IP CURL_LOCK_DATA_CONNECT Put the connection cache in the share object and make all easy handles using -this share object share the connection cache. Using this, you can for example -do multi-threaded libcurl use with one handle in each thread, and yet have a -shared pool of unused connections and this way get way better connection -re-use than if you use one separate pool in each thread. +this share object share the connection cache. + +Note that due to a known bug, it is not safe to share connections this way +between multiple concurrent threads. Connections that are used for HTTP/1.1 Pipelining or HTTP/2 multiplexing only get additional transfers added to them if the existing connection is held by |