>
> If you want to disable debugging for performance reason, you don't want to generate
> the debug string because String manipulation is expensive in Java, so it makes
> sense from a performance point of view to use the construct Thomas proposed
> rather than filtering at the Log class level.
>
Thats certainly a fair point. My experience with performance was client side java (yes,
we auto deployed swing.jar to IE4, gawd!)
If you bring the java console up in IE4 and log to it, everything starts to grind
incredibly slowly. So we just wanted it switched on or off. Hence the filtering
approach. But this was for debugging, not logging - which I would have thought would
be enabled in general.
If the logging is affecting performance server side then thats a big log being
generated - Id say!!
But every little bit counts.
cheers
Alan
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/[email protected]/>
List Help?: [EMAIL PROTECTED]
