Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: Cookie storage customization?
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Daniel Stenberg via curl-library <curl-library_at_lists.haxx.se>
Date: Sat, 18 Sep 2021 12:45:37 +0200 (CEST)
On Sat, 18 Sep 2021, Isaac Jurado wrote:
> There are two main goals in my case:
>
> 1. Minimize the amount of "active" sessions to against a domain
> 2. Minimize the amount of authentication "dances"
You seem to also want libcurl-applications used in *separate processes* using
shared cookie handling? I think that's the key here.
> With SQLite based approach, cookie modifications are almost immediately
> visible to the rest of the processes.
SQLite is not what makes that work, it is having the cookie "engine" shared
between multiple processes. Like a "share object" that works across process
boundaries. Is it not? SQLite just happens to be one technical solution to
storage and you could achieve the same thing using something else.
Your focus on replacing the text file fooled me, since that's just how we
export cookies when closing a handle, and replacing that with something SQL
will not get you the above mentioned features. You don't seem to talk about
changing how cookies are exported when a handle is closed.
Do I understand this correctly?
Date: Sat, 18 Sep 2021 12:45:37 +0200 (CEST)
On Sat, 18 Sep 2021, Isaac Jurado wrote:
> There are two main goals in my case:
>
> 1. Minimize the amount of "active" sessions to against a domain
> 2. Minimize the amount of authentication "dances"
You seem to also want libcurl-applications used in *separate processes* using
shared cookie handling? I think that's the key here.
> With SQLite based approach, cookie modifications are almost immediately
> visible to the rest of the processes.
SQLite is not what makes that work, it is having the cookie "engine" shared
between multiple processes. Like a "share object" that works across process
boundaries. Is it not? SQLite just happens to be one technical solution to
storage and you could achieve the same thing using something else.
Your focus on replacing the text file fooled me, since that's just how we
export cookies when closing a handle, and replacing that with something SQL
will not get you the above mentioned features. You don't seem to talk about
changing how cookies are exported when a handle is closed.
Do I understand this correctly?
-- / 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.htmlReceived on 2021-09-18