git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: http: a non-curl_multi interface?

From
Tay Ray Chuan <rctay89@gmail.com>
Date
Mar 3, 2009, 11:19 UTC
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:
Show 12 quoted lines
> 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
Previous: Daniel Stenberg
Message 3 of 3 in “http: a non-curl_multi interface?”
  1. Tay Ray ChuanMar 2, 2009
  2. Daniel StenbergMar 2, 2009
  3. Tay Ray ChuanMar 3, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.