[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: Brian Holmes <svndev_at_gmail.com>
Date: 2005-07-22 00:16:23 CEST

On 7/21/05, Greg Hudson <ghudson@mit.edu> wrote:
> On Thu, 2005-07-21 at 14:51 -0500, Ben Collins-Sussman wrote:
> > > How does the receiving string know when one log message ends and
> > > another one begins?
> [I meant to write "receiving stream" there.]
> > I apologize for my ignorance. Why is this important?
> > A process wants to push a message (some number of bytes, usually
> > ending in \n) into a stream_t. Who cares where the message
> > 'dividers' are?
> If you're logging via syslog(), you want to call syslog() with a
> complete log message, and not include a newline. I assume Windows event
> logging is similar.
> (I really advise learning about syslog() if you're not already familiar
> with it.)

Yes, we can but that doesn't mean we have to. Just because there are
extra features to syslog() doesn't mean we have to fully use them. We
could also attach binary data to our log messsages in Windows but we
don't need to. We really just want to support the interface enough to
get our one line message out.

Why can't a "complete log message" be written without new lines in the middle?

- Brian Holmes

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 22 00:17:52 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.