curl_interface is not thread safe about curlcpp

[JosephP91]

Ho sarum9in!
Yes, I know it's not thread safe and I was just thinking of adding support for it :)

[sarum9in]

I tried to find a commit with fix, but latest one is dated "Oct 19" and not related to this bug. What closes it?

[susnux]

I am also interested in this and want to know if it is fixed?
(I have a multi threaded application where I want to use it, at the moment I work with mutexes (maybe dirty)).

[sarum9in]

You can verify that yourself.
https://github.com/JosephP91/curlcpp/blob/master/include/curl_interface.h
is inherited by https://github.com/JosephP91/curlcpp/blob/master/include/curl_easy.h#L853

So it means that for every easy object creation/destruction global_init and global_destroy will be called.
I checked their implementation, they use non-atomic non-locked integer counter + they call non-thread-safe init/destroy functions of underlying SSL library. So it it thread-hostile to use them like in this library, you can't use it from different threads reliably.