Return-Path: <apr@apr.cs.com.uy>
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 10436 invoked from network); 12 Jun 2000 14:09:40 -0000
Received: from mail.cs.com.uy (qmailr@206.99.51.141)
  by locus.apache.org with SMTP; 12 Jun 2000 14:09:40 -0000
Received: (qmail 31646 invoked from network); 12 Jun 2000 14:09:21 -0000
Received: from cs.cs.com.uy (206.99.51.130)
  by mail.cs.com.uy with SMTP; 12 Jun 2000 14:09:21 -0000
Received: (qmail 57036 invoked from network); 12 Jun 2000 14:09:21 -0000
Received: from apr.cs.com.uy (206.99.51.131)
  by cs.cs.com.uy with SMTP; 12 Jun 2000 14:09:21 -0000
Received: (from apr@localhost)
	by apr.cs.com.uy (8.8.5/8.8.5) id LAA31942;
	Mon, 12 Jun 2000 11:09:21 -0300
Date: Mon, 12 Jun 2000 11:09:20 -0300
From: "Alejandro P. Revilla" <apr@cs.com.uy>
To: Stefano Mazzocchi <stefano@apache.org>
Cc: cocoon-dev@xml.apache.org
Subject: Re: C2 Logging
Message-ID: <20000612110920.B30069@cs.com.uy>
Mail-Followup-To: Stefano Mazzocchi <stefano@apache.org>,
	cocoon-dev@xml.apache.org
References: <NIEDJHCDBNGHNIOELIFFKEDIGDAA.david@i2a.com>
 <Pine.LNX.4.10.10005242338001.2067-100000@localhost.localdomain>
 <20000525130425.L4830@cs.com.uy> <39437E3F.8735F617@apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <39437E3F.8735F617@apache.org>;
 from Stefano Mazzocchi on Sun, Jun 11, 2000 at 01:55:43PM +0200
X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N

I'm reposting, my original reply didn't get thru (although my qmail says :
Jun 11 13:06:37 csdev qmail: 960739597.708046 delivery 613: success: 63.211.145.10_accepted_message./Remote_host_said:_250_ok_960739596_qp_17133/ ). 
Sorry if you end up with two different messages (I didn't saved my original
reply...:blush: )

> 
> Uh, found this very old message I flagged for comment. Sorry. Better
> later than never :)
> 
Nice to get a response. Thanks!

> 
> Sounds very much like Avalon's Omero, doesn't it?
>  
Not really. Omero seems to be "LogLevel" based. jPOS's logger
is tag based, you can always use <information>, <warning>, <debug>
and it's up to your LogListener to filter and format desired messages.

It can be easily adapted to generate SAX events that would simplify
custom LogListeners creation.

> 
> Hmmmm, kind of verbose.
>  
It's up to your LogListener to filter and format 
desired messages. Your logged Objects may implement
Loggeable with a not-so-verbose output.

> 
> Hmmmm, may create performance problems.
>  
LogListeners can be decoupled from Logger thread (OperatorLogListener 
actually does that to avoid delays while sending and batching e-mail
messages). You can even check for listeners (Logger.hasListeners() 
method) to avoid LogEvent creation.

> 
> Ok, Fede, take a look and contact Alejandro if interested.
> 
Hey, no rocket science here :-), it's extremely simple, you can 
give it a simple look and possibly cut-and-paste a few lines of 
code (i.e. some parts of OperatorLogListener can be used 
to replace those "Fill me" on Omero's MailToWriter).

>
> (Cocoon2 will probably use Avalon so the logging part will be inherited
> directly)
> 
I'm sure that's the way to go. 

--Alejandro