Re: [Edbrowse-dev] curl handles and general comms design

[Chris Brannon <chris@the-brannons.com>]

Adam Thompson <arthompson1990@gmail.com> writes:

> To solve the parallel curl handles accessing cookie databases issue,
> there's also the curl-shared interface.
> I believe this can be used with the curl-multi interface since the curl-multi
> interface is single-threaded so no need for mutexes etc.

We're using that now, but with curl easy handles, rather than curl
multi.  I don't know what would be involved in moving over to curl multi.

> What this all means I think is that, by combining both interfaces,
> we should be able to create a single-threaded, essentially async, comms layer.

The one problem is that you cannot share persistent connections across
curl easy handles.

Basically, you create a curl multi handle, and then add curl easy
handles to it.  So when would we create the individual curl easy
handles?

-- Chris