Re: [PATCH] http.c: clear the 'finished' member once we are done with it

From: Daniel Stenberg <daniel@haxx.se>
Date: May 24, 2022, 06:31 UTC
Message-ID: <q274s3nn-pp38-4sn-53ro-o2q63447r341@unkk.fr>
In-Reply-To: <xmqqa6b7lrw6.fsf@gitster.g>

On Mon, 23 May 2022, Junio C Hamano wrote:

Show 7 quoted lines

>> It calls into cURL, which I suspect has a multi-threaded mode of
>> operation,
>
> https://curl.se/libcurl/c/threadsafe.html ;-)
>
> My understanding is that what we have is pretty much select() driven 
> single-threaded multi-fd transfer.

Confirmed. libcurl *can* use threads (if built that way), but the only use it has for such subthreads is for resolving host names. libcurl, its API and its callbacks etc always operate in the same single thread.

-- 
  / daniel.haxx.se

$ 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.