Hello! We've run into an issue [1] in rust-lang/cargo's usage of curl
where timeouts are triggering when the filesystem is quite slow. I
believe the cause for this is that we have a multi socket interface
and whenever a transfer finishes we synchronously decompress it and
write it out to the filesystem. It looks like the timeout timers keep
running while we're doing filesystem operations, which means the next
time we come back to check the socket states we get a timeout error.

To that end, I was curious to clarify a bit about this usage:

1. Is there a way to across-the-board pause timeouts? For example just
before we do synchronous operations we could pause everything and then
unpause it soon afterwards.

2. Failing a "one method" solution, would `curl_easy_pause` work for
this purpose? If we paused everything just after we did our network
activity and repaused it when it was finished, would `curl_easy_pause`
also pause timeout timers?

3. And failing those two solutions, is this simply a case where the
progress callback is recommended to implement custom timeout
strategies?

Thanks!

[1]: https://github.com/rust-lang/cargo/issues/6125
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2018-10-03