Jakub Narebski wrote:
> One solution I can think of (still backwards incompatibile) would be to
> provide $per_request_config variable, which would hold anonymous sub
> with parts of config that need to be done per request (this should work
> with global variables (our), but I think it wouldn't work with lexical
> variables (my)). For example gitolite's contrib/gitweb/gitweb.conf would
> then include:
>
> $per_request_config = sub {
> $ENV{GL_USER} = $cgi->remote_user || "gitweb";
> }
How would that interact with caching? i.e., how would whatever caching
engine is used learn that $cgi->remote_user is part of the key needed to
uniquely determine a response?
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html