On 1/29/2015 11:29 PM, RaJ M wrote:
> I am using curl_multi_wait() + curl_multi_perform() to perform
> continuous HTTP transfers. (All transfers to a single HOST:PORT) That
> creates multiple TCP connections. (as it should/can)
>
> Does libcURL multi interface allow user to configure it to restrict to
> strictly use only one TCP connection across easy handles being added ?
> If it does, are there any example programs ?

Check out CURLMOPT_MAX_HOST_CONNECTIONS [1]. Enable it on the multi
handle via curl_multi_setopt. There may be some caveats if
CURLMOPT_PIPELINING is enabled as well. It was discussed last year [2]
but I'm not sure of the status.

> If it doesn't, is it inappropriate to just set options via
> curl_easy_setopt (including CONNECT_ONLY) and get the libcURL socket
> using CURLINFO_LASTSOCKET and do own send(), recv() instead of
> curl_easy_perform to avoid blocking call ?

Don't reinvent the wheel ok :)

[1]: http://curl.haxx.se/libcurl/c/CURLMOPT_MAX_HOST_CONNECTIONS.html
[2]: http://curl.haxx.se/mail/lib-2014-10/0262.html

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2015-01-30