cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom Klaasen (TeleRelay)" <>
Subject RE: Cocoon 2.0 Scalability Disappointment
Date Wed, 05 Dec 2001 15:40:26 GMT

> -----Original Message-----
> From: [] 
> > I think this can be an appropriate timing to start cleaning up the 
> > logging code. We have to find a policy and stick to it: I 
> tend to say 
> > that we should *always* do a isDebugEnabled() or a isInfoEnabled() 
> > before spitting out Strings. I'm not that sure that such a 
> policy should 
> > be enforced for levels of warn and above.
> I totally agree.
> This sped up my app quite a bit.
> Maybe a static utility method that does the check is nicers 
> than many ifs.

How would you do that? The reason for calling the "isDebugEnabled()" is
exactly to avoid all the work involved in concatenating the Strings
you're providing as parameter. And this would also be done with static


To unsubscribe, e-mail:
For additional commands, email:

View raw message