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

Re: libsvn_repos logging -- design problems

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-07-15 18:04:44 CEST

On Jul 15, 2005, at 10:53 AM, John Peacock wrote:
> I think the public API is too low level to begin with. Each
> process should be calling a logger, which is the only code that
> handles writing and the only code which knows to where the log is
> being written.

What is a 'logger'? A whole new svn-logging-daemon process?

I see only two options: write a whole new logging daemon, or use
some sort of file-locking to mediate access.

> It would also solve the apr_psprintf performance issues if there
> was an opaque logger object that contained the loglevel, so that
> all code could do something like this [horrible pseudocode]:
> if this_event_level < logger.loglevel
> logger.log_error(moderately expensive apr_psprintf)

Yes, that's basically what Branko was suggesting.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 15 18:05:24 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.