It's always been a big performance problem, not matter what's backing the system output, to use System.out in web apps. I'm confused as to why logging must be synchronous and couldn't be optimized/buffered like other logging implementations to negate this issue within GF.
>sdo wrote:
>>
>> The "something" that GF is doing is using the logging framework for stdout
>> as well as stderr. That means all messages to stdout get logged with a
>> timestamp, a thread ID, and other information (which I must admit is quite
>> useful for debugging).
>
>I agree that these are useful bits of information. So dropping the
>logging framework for stdout does not sound like the best way to go.
>
>Nevertheless it would be nice if this could be switched off. I think it
>should even be switched off by default. Otherwise GlassFish would get
>too much negative press (and I doubt reviewers will go into too much
>trouble trying to figure this out).
>
>On the other hand this feature should be made more public. For
>preventing negative feedback as well as to highlight another feature
>where GlassFish does a nice job. S.o. should blog about it ;-)
>
>BTW: I assume that a lot of people use log4j and stdout as one of the
>appenders. Probably not the best use of log4j but nevertheless a common
>one. Another reason why this feature should be switched off by default,
>IMHO.
>
>
>Wolfram
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>