From: Tay Ray Chuan <rctay89@gmail.com>
Date: Tue, 03 Mar 2009 11:19:33 GMT
Subject: Re: http: a non-curl_multi interface?
Message-ID: <be6fef0d0903030319k46bd5f9bx69148a920213038d@mail.gmail.com>
In-Reply-To: <alpine.DEB.1.10.0903021412120.15587@yvahk2.pbagnpgbe.fr>

Hi,

On Mon, Mar 2, 2009 at 9:26 PM, Daniel Stenberg <daniel@haxx.se> wrote:
> What I don't quite grasp (and I must admit I have not followed the critique
> on this matter) is why using the multi interface of libcurl is a problem to
> anyone as all libcurl versions in modern times features it. And if you have
> a libcurl with it working badly, you have a too old libcurl anyway and
> should rather upgrade...
>
> ...
>
> I don't see how that is true. In fact, properly used I would claim that an
> application using the multi interface would in general use less connections
> and do more connection re-use than otherwise. But of course it depends on a
> lot of factors.

Hmm, there aren't any very obvious benefits are there?

In that case, I guess, an re-organization of the http api/curl usage
would be more useful to git.

-- 
Cheers,
Ray Chuan