I'm wondering what are consequences of late curl_multi_perform call. I guess
that it may cause some timeouts to occur later than it should i.e. we set
CURLOPT_TIMEOUT for 60s, but whole operation lasted 62s. But are there any
significant consequences for ongoing transfer? Say we are downloading
Marcin Adamski wrote:
I'm wondering what are consequences of late curl_multi_perform call. I guess
that it may cause some timeouts to occur later than it should i.e. we set
CURLOPT_TIMEOUT for 60s, but whole operation lasted 62s. But are there any
significant consequences for ongoing transfer
On Mon, 3 Oct 2011, Marcin Adamski wrote:
I'm wondering what are consequences of late curl_multi_perform call. I guess
that it may cause some timeouts to occur later than it should i.e. we set
CURLOPT_TIMEOUT for 60s, but whole operation lasted 62s. But are there any
significant consequences
On Mon, 3 Oct 2011, Rich Gray wrote:
Before version 7.20.0: If you receive CURLM_CALL_MULTI_PERFORM, this
basically means that you should call curl_multi_perform again, before you
select() on more actions.
I'm trying to figure out what this really means.
If you use a recent libcurl I
Daniel Stenberg wrote:
On Mon, 3 Oct 2011, Rich Gray wrote:
Before version 7.20.0: If you receive CURLM_CALL_MULTI_PERFORM, this
basically means that you should call curl_multi_perform again, before
you select() on more actions.
I'm trying to figure out what this really means.
If you use a
