Daniel Stenberg wrote:

> I do however think that we should remove the CURLM_CALL_MULTI_PERFORM
> return code one day and make curl_multi_perform() perform as much as
> possible instead and only return when it would otherwise have to block
> waiting on a socket. It is what the apps want anyway and it'll make
> nicer apps.
>
     Ok, there's always more than one way to do it.

> I meant that I don't understand what your patch and suggestion does
> and what goodness it brings!

    My basic point is that we can have a way to run those handles which
don't wait events without change the current multi_runsingle() or
multi_perform()'s implementation, but as you (and as i) said before,
making multi_perform() perform as much as possible until it does block
on sockets is also a good idea, it's up to your decision.

--
Sun Yi Ming.