On Thu, 16 Sep 2021, Isaac Jurado wrote:
Yes, in-memory handle reuse and share handles solve all cookie problems
within a single process, multiple thread environment.
However, to share cookies across concurrent heterogeneous process, I
understand that share handles are not enough.
No, that's very true. But I also don't think that replacing the flat text file
with a SQL database will be much of an improvement either.
I would love to learn what problems replacing the storage will solve for you.
While I would never even consider introducing SQLite as a dependency to
solve just this edge case, I was wondering if adding more "extension points"
for cookie management could be an interesting idea from the libcurl design
point of view.
We're usually open to discuss improvements; be it in functionality, in
performance, in API or in accessibility. But I also think that every suggested
change needs to be properly motivated and there needs to be a clear and real
use case for every proposal.
--
/ daniel.haxx.se
| Commercial curl support up to 24x7 is available!
| Private help, bug fixes, support, ports, new features
| https://curl.se/support.html
--
Unsubscribe: https://lists.haxx.se/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
