[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Logging: home-grown mechanism or syslog/event-log?

From: Michael R Sweet <mike_at_easysw.com>
Date: 2005-07-24 15:38:26 CEST

Branko Čibej wrote:
> Michael R Sweet wrote:
>> Ben Collins-Sussman wrote:
>>> ...
>>> This doesn't seem like very much code to me. I agree that maybe
>>> this could be sublimated into APR, but it also seems pretty general
>>> and simple. To me, the "big coding task" that's going to create
>>> tons of churn (and require maintenance) is teaching our servers to
>>> *call* the logging API in a million places. The actual logging
>>> infrastructure described above, even if homegrown, seems pretty tiny
>>> to me.
>> My $0.02: take the existing httpd low-level logging code and move it
>> to APR. Then have the httpd and Subversion logging APIs (which would
>> just be thin glue layers) use the APR log API to actually log the
>> individual messages.
> Oh sure, and wait for 2 years until Subversion and HTTPD both catch up
> with whichever version of APR happens to include that API. It certainly
> wouldn't happen before httpd-2.2 and svn-2.0.

Nothing says you can't design it that way - copy the httpd code and
give it a private SVN API prefix, and then when APR catches up you
can remove the private API without affecting the public one...

At least you'd be starting with existing, working code that is
well-suited to different kinds of logging...

Michael Sweet, Easy Software Products           mike at easysw dot com
Internet Printing and Publishing Software        http://www.easysw.com
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jul 24 15:40:11 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.