I would like to have the possibility to disable the connections pool. I
mean one easy handle has its own physical connection which is not shared
with other handles. Pooling connections assumes that all connections are
equivalent which is not my case.
The reason is, as I explained before, each physical connection is pinned to
a web server behind the load balancer and each HTTP request should be sent
to the web server where the user was authenticated and has his session. So
in my case, all physical connections are not equivalent.

On Mon, Mar 7, 2016 at 4:41 PM, Daniel Stenberg <daniel_at_haxx.se> wrote:

> On Mon, 7 Mar 2016, Pierre Brico wrote:
>
> So my problem is that libcurl manages its own connections pool. In this
>> pool, there are connections to the web server 1 and the web server 2 but
>> each virtual user has its HTTP session on one server (there is no
>> replication between web servers). So, for example, if libcurl takes a
>> connection to server 1 and the virtual user has its current HTTP session on
>> server 2, the web application blocks the request because the user is not
>> authenticated on this server...
>>
>> If this is not something you want to change in libcurl, could you help me
>> pointing out in the sources where I can change this behavior?
>>
>
> I'm not sure what "this" means here. Can you specify what you would like
> libcurl to do here for you?
>
> --
>
> / daniel.haxx.se
> -------------------------------------------------------------------
> 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