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

Re: [PATCH] Fix HTTP request result processing after slot reuse

From
Junio C Hamano <junkio@cox.net>
Date
Jan 31, 2006, 21:39 UTC
Message-ID
<7v64o0ulfu.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20060131190655.GE3873@reactrix.com>
Nick Hengeveld <nickh@reactrix.com> writes:
> Add a way to store the results of an HTTP request when a slot finishes
> so the results can be processed after the slot has been reused.
>
> Signed-off-by: Nick Hengeveld <nickh@reactrix.com>

I do not claim I understand this part of the code well, but it feels awkward to see that a problem caused by a structure being reused can be solved by having a pointer from that structure that points at a static location.

These static variables are probably correct, provided if fetch_index, fetch_indices and friends do not recurse into themselves, but it just gives me this funny feeling...

Care to enlighten me, please?
Previous: Nick HengeveldNext: Nick Hengeveld
Message 2 of 3 in “Fix HTTP request result processing after slot reuse”
  1. Fix HTTP request result processing after slot reuseNick Hengeveld, Jan 31, 2006
  2. Junio C HamanoJan 31, 2006
  3. Nick HengeveldFeb 1, 2006

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.