[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 -- rethunk

From: John Szakmeister <john_at_szakmeister.net>
Date: 2005-07-18 12:37:17 CEST

On Sunday 17 July 2005 22:02, Christopher Ness wrote:
> On Sat, 2005-07-16 at 10:17 -0400, John Szakmeister wrote:
> > Sure there is. Having the log baton separated from the repository baton
> > means that you can potentially use logging for other purposes. For
> > example, clients could use it for their own debugging purposes (i.e., it
> > might be easier to get a "traceback" to help track down bugs), or we
> > could provide a general logfile via /etc/subversion for logging events
> > that don't have a
> ********** | **********************
> * Client * | * Apache || SVNserve *
> ********** | **********************
> Do you want to allow a client be able to add a entry to a repository
> server log? That is how I interpreted it.

Looks like Ben already chimed in, but no, I wasn't proposing to let the client
log information into the server's log file. I was really looking for a
facility to support logging on the client-side (separate than the server) as
well. IOW, let's write one facility that can be used by our clients for
other purposes outside of server-side logging.

> Why would the client log this?  It seems you think they should - other
> than the fact client logging would be nice.  The server process should
> be logging these bad URL's.  Correct?

The point was that if we tuck away the internals of logging behind an
svn_repos_t, then we can't really share the logging mechanism with the
client. I think that the ability to log stuff to a file or stdout would be a
useful tool for clients, so I was looking to keep that door open.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 18 12:38:01 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.