While I see this picture, - and I'm just curious - what was the reason to implement resource locking (mutexes) not by a backend but let the user do it on their own via callbacks? (ref: curl.se/libcurl/c/CURLSHOPT_LO…)
hm, I always thought the mutex implementation only differed by platform.
I'm facing a similiar issue with github.com/Gottox/sqsh-tools and wondering if I should provide callback interfaces or instead use pthread mutexes on unix and win32 mutexes on windows.
I love #curl. It is a very nice and useful piece of #softwae. I use it i #C++, #Java, #PHP and other for any type of secure connection. Keep on with that great job!
Enno T. Boland
in reply to daniel:// stenberg:// • • •CURLSHOPT_LOCKFUNC
curl.sedaniel:// stenberg://
in reply to Enno T. Boland • • •Enno T. Boland
in reply to daniel:// stenberg:// • • •hm, I always thought the mutex implementation only differed by platform.
I'm facing a similiar issue with github.com/Gottox/sqsh-tools and wondering if I should provide callback interfaces or instead use pthread mutexes on unix and win32 mutexes on windows.
GitHub - Gottox/sqsh-tools: 🗜️ fast r/o squashfs implementation written in C. BSD-2 licensed; complete, fast, easy
GitHubdaniel:// stenberg://
in reply to Enno T. Boland • • •Enno T. Boland
in reply to daniel:// stenberg:// • • •saturata
in reply to daniel:// stenberg:// • • •CatSalad🐈🥗 (D.Burch)
in reply to daniel:// stenberg:// • • •daniel:// stenberg://
in reply to CatSalad🐈🥗 (D.Burch) • • •daniel:// stenberg://
Unknown parent • • •open source free software compression library
Contributors to Wikimedia projects (Wikimedia Foundation, Inc.)