It is. At least for kernel.org, the issue isn't that CGI is expensive,
its that I/O is expensive.
IMO yes, since most major browsers, caches, and spiders support these
headers.
Yes, a good point to note.
Mostly true: you must also consider HTTP_ACCEPT
That would be a good start, and suffice for many cases. If the CGI can
simply stat(2) files rather than executing git-* programs, that would
increase efficiency quite a bit.
A core problem with cache hints via HTTP headers (last-modified, etc.)
is that you don't achieve caching across multiple clients, just across
repeated queries from the same client (or caching proxy).
At least for the RSS/Atom feeds and the git main page, it makes no sense
to regenerate that data repeatedly.
Internally, gitweb would need to do a stat() on key files, and return
pre-generated XML for the feeds if the stat() reveals no changes. Ditto
for the front page.
CGI version of gitweb.
But again, mod_perl vs. CGI isn't the issue.
Jeff
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html