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

Re: Gitweb - caching

From
JGJeff Garzik <jeff@garzik.org>
Date
Dec 31, 2006, 20:01 UTC
Message-ID
<4598171D.2040002@garzik.org>
In-Reply-To
<20061231174123.GI6558@localhost>
Robert Fitzsimons wrote:
Show 12 quoted lines
>> Thoughts or comments are welcome.
> 
> Interesting work, John.  Some initial comments:
> 
> * It's a very intrusive set of changes.
> * An infinite expiry date isn't valid for all pages.
> * The other HTTP headers can change depending on the page returned.
> * A single cache directory is going to have problems as the number of
>   cached files grows.
> 
> What are the benefits of doing this inside of gitweb instead of using
> something like mod_cache or mod_perl handlers?

Or wrapping the gitweb output inside cgicache: http://linux.yyz.us/projects.html

	Jeff
Previous: Robert FitzsimonsNext: Jakub Narebski
Message 3 of 4 in “Gitweb - caching”
  1. J.H.Dec 31, 2006
  2. Robert FitzsimonsDec 31, 2006
  3. Jeff GarzikDec 31, 2006
  4. Jakub NarebskiDec 31, 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.