>
> 1. MAX SOCKETS CHANGES
> While CURLMOPT_MAXCONNECTS imposes a limit on the number of sockets
> persisted, it does not regulate the maximum number of sockets that are in
> use at a given point in time. It is proposed that CURLMOPT_MAXCONNECTS be
> aliased/renamed CURLMOPT_MAXCONNECTS_SOFT, and that a new option,
> CURLMOPT_MAXCONNECTS_HARD would be introduced. The latter option would
> regulate the maximum number of open sockets at any given point in time.
> This will be necessary to eliminate the need for queuing requests at the
> application layer when the application wishes to throttle the number of
> underlying sockets.
>

Assuming this new option (CURLMOPT_MAXCONNECTS_HARD) will be supported when not using pipelining, will the client be able to prioritize queued requests or it is going to be a FIFO implementation?

Thanks,
Vladimir
                                               
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2012-07-24