On 6/14/2014 5:42 PM, Daniel Stenberg wrote:
> On Sat, 14 Jun 2014, Ray Satiro wrote:
>
>>> think we should call the progress callback again. Basically that
>>> could lead to the similar problem: return an error from another
>>> callback and yet you get the progress callback called again.
>>
>> Ok that works on the samples. Generally speaking though if a status
>> != CURLE_OK is passed to a done handler is it possible for that done
>> handler to return a result of CURLE_OK?
>
> Yes, that's up to the done handler.
>
>> I'm trying to figure out if there will still be a scenario where
>> Curl_pgrsDone() could be called with a bad status and whether or not
>> it's permissible in that case.
>
> It is for example possible in the FTP case where the problem isn't
> considered to be bad enough to tear down the control channel. That
> would not include CURLE_ABORTED_BY_CALLBACK though.
>

Thanks for the explanation, it gives me a better understanding of how
status can be handled. My only concern left would be for posterity,
should you think that's an issue. Otherwise this seems pretty much
firmed up.
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2014-06-16