On Aug 2, 2005, at 9:21 AM, C. Michael Pilato wrote:
>
> Ben, this may not be what you were talking about here, but I still
> think that a mod_dav_svn logging subsystem should understand
> httpd.conf directives for the log file locations and the log level,
> just like mod_rewrite does. Doing so allows administrators to decide
> if they want all their mod_dav_svn Subversion logs in one place, or if
> they want to distribute them based on URLs. With Apache's cascading
> configuration support, there's no point in *not* giving this
> flexibility.
I think everyone is assuming that we're planning to add a whole
"subsystem" to mod_dav_svn; that was never part of the plan. The
plan was to make mod_dav_svn write "client did an update" to the
standard apache accesslog, nothing more.
But, it sounds like people want us to make mod_dav_svn more complex
than that... to be able to write its own private logs as well. Once
again, I ask: is it worth reinventing logging functionality?
Figuring out how to write to logs atomically, creating new httpd
directives, worrying about rotation. Sure, I guess we could imitate
whatever mod_rewrite is doing, but it sort of defeats the whole goal
of not reinventing logging.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 2 16:47:55 2005