It looks now quite nice, but I'd like to see information about
dependencies for this feature in the commit message, something like:
This feature (terminating early with '304 Not Modified' in response
to 'If-Modified-Since' conditional request) requires having either
HTTP::Date module (from libwww-perl) or Time::ParseDate module.
If neither is present gitweb falls back to earlier behaviour of not
reacting to 'If-Modified-Since'.
Note also (although I'm not sure if it is worth mentioning in commit
message) that it doesn't save gitweb as much work as one could think,
because at this place the whole list of commits is already generated
and parsed. What we save is cost of running git-diff-tree for each
commit (we could do better here, I think), and of course bandwidth.
I wonder if it would be possible to separate this code into subroutine,
to make it possible to have support for "cache control" conditional
requests also in other cases where it might help (for the future of
course, not in this commit).
Perhaps if we run gitweb from Apache mod_perl in compatibility mode
(ModPerl::Registry) to use Apache Perl API to respond to
'If-Modified-Since' ($r->is_fresh or something). But that is also
just idea for the future improvement.
Here I think:
Acked-by: Jakub Narebski <jnareb@gmail.com>
Nitpick: either follow aligning on '=' characters, or skip it
altogether and always use one space before '=' in this fragment.
Good.
--
Jakub Narebski
Poland
--
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