Hi Daniel! Thank you for your reply!
Do you mean that although an explicit call to curl_global_init is not thread safe, an implicit call from, e.g., curl_easy_init is still thread safe? So that in a multi-threaded process I would not want to explicitely call curl_global_init but rather would call curl_easy_init and rely on the implicit initialization? Best, Konstantin On Mon, Jun 11, 2012 at 6:55 PM, Daniel Stenberg <[email protected]> wrote: > On Mon, 11 Jun 2012, Konstantin Miller wrote: > > the libcurl tutorial states that "libcurl is completely thread safe, >> except for two issues: signals and SSL/TLS handlers". On the other hand, >> the description of curl_global_init states: "This function is not thread >> safe. You must not call it when any other thread in the program (i.e. a >> thread sharing the same memory) is running. This doesn't just mean no other >> thread that is using libcurl." >> >> What is right? >> > > libcurl is completely thread safe, except for THREE issues: > - signals > - SSL/TLS handlers > - curl_global_init > > We should update the docs to specify this and nothing else! > > -- > > / daniel.haxx.se > ------------------------------**------------------------------**------- > List admin: > http://cool.haxx.se/list/**listinfo/curl-library<http://cool.haxx.se/list/listinfo/curl-library> > Etiquette: > http://curl.haxx.se/mail/**etiquette.html<http://curl.haxx.se/mail/etiquette.html> >
------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
