On Tue, Jul 23, 2013 at 11:26 AM, Daniel Stenberg wrote:
> On Tue, 23 Jul 2013, Justin Karneges wrote:
>
> I suggest a fix like the attached one, what do you think about it?
>>>
>>
>> Doesn't seem to work. I expect that my timer callback should get called
>> during curl_easy_pause() to set up a
On Tue, 23 Jul 2013, Justin Karneges wrote:
I suggest a fix like the attached one, what do you think about it?
Doesn't seem to work. I expect that my timer callback should get called
during curl_easy_pause() to set up a new timer? No call to my callback is
made. I sprinkled some debug prints
On Tue, Jul 23, 2013 at 4:39 AM, Daniel Stenberg wrote:
> On Mon, 22 Jul 2013, Justin Karneges wrote:
>
> Instead of curl_multi_socket_action() with CURL_SOCKET_TIMEOUT, it seems
>> the better answer is curl_multi_socket_all().
>>
>
> Right, that's a better work-around but if you have many handl
On Mon, 22 Jul 2013, Justin Karneges wrote:
Instead of curl_multi_socket_action() with CURL_SOCKET_TIMEOUT, it seems
the better answer is curl_multi_socket_all().
Right, that's a better work-around but if you have many handles running
that'll cause you quite a significant performance hit.
I
Instead of curl_multi_socket_action() with CURL_SOCKET_TIMEOUT, it seems
the better answer is curl_multi_socket_all().
On Mon, Jul 22, 2013 at 2:27 PM, Justin Karneges wrote:
> On Mon, Jul 22, 2013 at 1:38 PM, Daniel Stenberg wrote:
>
>> On Mon, 22 Jul 2013, Justin Karneges wrote:
>>
>> In ex
On Mon, Jul 22, 2013 at 1:38 PM, Daniel Stenberg wrote:
> On Mon, 22 Jul 2013, Justin Karneges wrote:
>
> In examining the source to libcurl, it appears that curl_easy_pause()
>> only sets some internal data and returns. That is, it does not actually run
>> the curl engine.
>>
>
> Hm, yes I thin
On Mon, 22 Jul 2013, Justin Karneges wrote:
In examining the source to libcurl, it appears that curl_easy_pause() only
sets some internal data and returns. That is, it does not actually run the
curl engine.
Hm, yes I think you're right. But libcurl doesn't know what "engine" that
should be r
Hi folks,
I'm returning CURL_READFUNC_PAUSE in my read function to tell curl to wait
until I have more data to send. I once I have data to send, I then call
curl_easy_pause() with the CURLPAUSE_SEND bit unset to resume the session.
However, my observation is that the session often gets "stuck" and
