From: Jeff Garzik <jeff@garzik.org>
To: Robert Fitzsimons <robfitz@273k.net>
Cc: "J.H." <warthog19@eaglescrag.net>, git@vger.kernel.org
Subject: Re: Gitweb - caching
Date: Sun, 31 Dec 2006 15:01:33 -0500 [thread overview]
Message-ID: <4598171D.2040002@garzik.org> (raw)
In-Reply-To: <20061231174123.GI6558@localhost>
Robert Fitzsimons wrote:
>> 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
next prev parent reply other threads:[~2006-12-31 20:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-31 10:30 Gitweb - caching J.H.
2006-12-31 17:41 ` Robert Fitzsimons
2006-12-31 20:01 ` Jeff Garzik [this message]
2006-12-31 20:52 ` Jakub Narebski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4598171D.2040002@garzik.org \
--to=jeff@garzik.org \
--cc=git@vger.kernel.org \
--cc=robfitz@273k.net \
--cc=warthog19@eaglescrag.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).