Hey,

For users of HTTP pipelining and for upcoming users of multiplexing, I'm
pondering on adding support for yet another bit in CURLMOPT_PIPELINE:

CURLPIPE_WAITFORIT (or a similar name) - the application prefers to have
libcurl wait for an existing connection to be finish its handshake/connection
and get the status about it to figure out if it should pipeline/multiplex over
it, rather than to create a new connection immediately if none exists to
multiplex or pipeline on.

The current behavior is to check if there's a connection available to
pipeline/multiplex on, and if not it will create a new connection (unless we
limit the number of connections).

Which behavior is the "best" one is bound to very between different use cases.
Is it better to wait to multiplex or is it better to instantly fire up a new
connection and use that?

I recall having people ask for this waiting behavior in the past.

-- 
  / daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html