logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <Vincent.Bourdar...@nokia.com>
Subject RE: High performance filters
Date Wed, 19 Jul 2006 15:21:43 GMT
This is the kind of answer I was afraid of ;)

But that is a very powerfull feature some of our (large) customers are asking for very loudly:
it gives both debug messages and good-enough performance for live systems.

Sure I could do it myself, but then that would not apply to already existing log4j-compliant
code :(

I'll ask to the dev mailing list, just in case...

Thanks for your help,

>-----Original Message-----
>From: ext Javier Gonzalez [mailto:jagonzal@gmail.com] 
>Sent: Wednesday, July 19, 2006 5:08 PM
>To: Log4J Users List
>Subject: Re: High performance filters
>On 7/19/06, Vincent.Bourdaraud@nokia.com 
><Vincent.Bourdaraud@nokia.com> wrote:
>> I hope this is clear enough :)
>It is, and your problem looks very non-trivial :)
>To me, it looks like you need to implement your own filtering 
>before invoking buildDebugMessage(), since to access the log4j 
>framework you need to pass an object (whose construction is 
>what you want to avoid).
>Javier González Nicolini
>To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>For additional commands, e-mail: log4j-user-help@logging.apache.org

To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org

View raw message