2018-04-06 07:51:42 UTC
I filed a bug report on red hat bugzilla regarding the curl_easy_pause inefficiency as described in https://curl.haxx.se/libcurl/c/curl_easy_pause.html <https://curl.haxx.se/libcurl/c/curl_easy_pause.html> page:https://bugzilla.redhat.com/show_bug.cgi?id=1563130 <https://bugzilla.redhat.com/show_bug.cgi?id=1563130>
It seems that this has been fixed in this commit: https://github.com/curl/curl/commit/b5478a0e033e70478f1c935719bf2e29fda02526 <https://github.com/curl/curl/commit/b5478a0e033e70478f1c935719bf2e29fda02526>But the assigned person is concerned that pushing the bug fix might introduce an observable change in behavior likely to trigger bugs in third party code. Maybe you could advise on this?
Also, is there a possible workaround with a limited performance impact within version 7.29.0 (the one mentioned on the curl_easy_pause.html page of calling curl_multi_socket_all is said to have "a rather hefty performance penalty")?