aboutsummaryrefslogtreecommitdiff
path: root/docs/FAQ
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2005-04-13 08:47:59 +0000
committerDaniel Stenberg <daniel@haxx.se>2005-04-13 08:47:59 +0000
commita19b23b59f6df1e3c2b584e3b05a0dba389b5f64 (patch)
tree7a1af01f1fd1a8bdb64c8fd925be95310fddfeb3 /docs/FAQ
parent4e26b2a65b8946ca32479addeda2754a14587ba7 (diff)
extended the multi-thread explanation
Diffstat (limited to 'docs/FAQ')
-rw-r--r--docs/FAQ14
1 files changed, 11 insertions, 3 deletions
diff --git a/docs/FAQ b/docs/FAQ
index 1fc30c14f..3c6dd9d8b 100644
--- a/docs/FAQ
+++ b/docs/FAQ
@@ -1,4 +1,4 @@
-Updated: April 11, 2005 (http://curl.haxx.se/docs/faq.html)
+Updated: April 13, 2005 (http://curl.haxx.se/docs/faq.html)
_ _ ____ _
___| | | | _ \| |
/ __| | | | |_) | |
@@ -745,8 +745,16 @@ FAQ
programs. libcurl will use thread-safe functions instead of non-safe ones if
your system has such.
- We would appreciate some kind of report or README file from those who have
- used libcurl in a threaded environment.
+ If you use a OpenSSL-powered libcurl in a multi-threaded environment, you
+ need to provide one or two locking functions:
+
+ http://www.openssl.org/docs/crypto/threads.html#DESCRIPTION
+
+ If you use a GnuTLS-powered libcurl in a multi-threaded environment, you
+ need to provide locking function(s) for libgcrypt (which is used by GnuTLS
+ for the crypto functions).
+
+ [informative link missing]
5.2 How can I receive all data into a large memory chunk?