On 09.09.19 22:10, John Snow wrote:
>
>
> On 8/27/19 12:34 PM, Max Reitz wrote:
>> curl_multi_do_locked() currently marks all sockets as ready. That is
>> not only inefficient, but in fact unsafe (the loop is). A follow-up
>> patch will change that, but to do so, curl_multi_do_locked() needs to
On 8/27/19 12:34 PM, Max Reitz wrote:
> curl_multi_do_locked() currently marks all sockets as ready. That is
> not only inefficient, but in fact unsafe (the loop is). A follow-up
> patch will change that, but to do so, curl_multi_do_locked() needs to
> know exactly which socket is ready; and t
