From 2ac560e58bb92c8225919f782e18fc93b436b9d9 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Fri, 4 Aug 2006 13:06:36 +0000 Subject: even when we get a single connection to deal with, we must still check for timeout'ed connections and possibly deal with them too --- lib/multi.c | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/lib/multi.c b/lib/multi.c index fa88cdaab..4e6efecd1 100644 --- a/lib/multi.c +++ b/lib/multi.c @@ -1203,10 +1203,9 @@ static CURLMcode multi_socket(struct Curl_multi *multi, last */ singlesocket(multi, data->set.one_easy); - *running_handles = multi->num_alive; - - /* or should we fall-through and do the timer-based stuff? */ - return result; + /* Now we fall-through and do the timer-based stuff, since we don't want + to force the user to have to deal with timeouts as long as at least one + connection in fact has traffic. */ } /* -- cgit v1.2.3