Hi Isaac,

To my knowledge, the multi interface allows just you to manipulate several
easy handles at a time (asynchronously) but doesn't give access to the
underlying connection to the server. Am I wrong ?

Kind regards,
Pierre

On Mon, Mar 7, 2016 at 9:19 AM, Isaac Boukris <iboukris_at_gmail.com> wrote:

> Hi,
>
> On Mon, Mar 7, 2016 at 1:15 AM, Daniel Stenberg <daniel_at_haxx.se> wrote:
> > On Sun, 6 Mar 2016, Pierre Brico wrote:
> >
> >> So my question is: is it possible to link one connection to one CURL
> >> handle (no pool usage)?
> >
> >
> > In theory it should be fairly easy to have each easy handle use its own
> > connection pool, as that is already what libcurl does when using the easy
> > interface - there's just no way to tell libcurl to act like that. We've
> not
> > seen users request this before so it hasn't been made possible.
>
>
> I currently have a similar requirement and I'm testing the approach of
> coupling each easy handle with its own multi handle (using
> curl_multi_socket_action).
> It works ok so far, though I wonder how well it would scale (and you
> could still share other stuff, like DNS resolving and TLS sessions via
> the share interface).
>
> Regards,
> Isaac B.
> -------------------------------------------------------------------
> List admin: https://cool.haxx.se/list/listinfo/curl-library
> Etiquette: https://curl.haxx.se/mail/etiquette.html

-------------------------------------------------------------------
List admin: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2016-03-07