> curl already has a connection pool
Good to know
> nobody has yet signed up to actually implement it
Yes, sure;But pretty happy that this proposal  drew your attention anyway ;)
Regards 
Xavier 

-------- Message d'origine --------
De : Daniel Stenberg <daniel_at_haxx.se>
Date : 16/12/2015 11:24 (GMT+01:00)
À : "Xavier !! <M X >" <mxav_at_yahoo.com>, the curl tool <curl-users_at_cool.haxx.se>
Objet : Re: curl waits for stdin to "EOF" before firing requests when "-K -" is used to read config from stdin

On Wed, 16 Dec 2015, Xavier !! <M X > via curl-users wrote:

> "named pipe" or stdin, that was exactly the point  (Of course, EOF sent to
> curl trough "named pipe" or stdin would tell curl to quit) What would/should
> happen when URLs set to distinct HOSTs/IPs are met in random orders from
> stdin ?

> Should curl keep n distinct connexions opened, or should it close the TCP
> connexion when the next HOST has a different "ip:port" than the previous URL
> ?

curl already has a connection pool that is always used, I don't see how this
suggested feature would need any particular change to that. The connection
pool holds N connections alive after use in case they're reused in a
subsequent request.

But note that we're so far only discussing a possible feature here, nobody has
yet signed up to actually implement it.

-- 
  / daniel.haxx.se

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-users
FAQ: http://curl.haxx.se/docs/faq.html
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2015-12-16