Craig McClanahan wrote:
> Jan Luehe wrote:
>> [snip]
>> I think regardless of whether access logging is on or off by default,
>> once it is
>> on (either by default or by configuration), developers expect
>> immediate updates.
>>
>> I think we need to do a survey of how useful access logging is during
>> development,
>> and how much of a performance penalty people are willing to pay for it.
>>
>> Tomcat disables it by default, and nobody has ever complained about it.
>>
> There's a reason for that. The important log file during development
> is the system log, not the access log ... so you can see exception
> messages and the like. That's also why tools like NetBeans and
> Creator give you direct access to the system log, but not to the
> access log.
>
> I'd vote for access log disabled by default. But also, given the
> theory that the only time you'd want the access log enabled is a
> production environment where performance is important, I'd also vote
> for configuring the default enabled behavior to maximize performance.
That is a consistent opinion. I like that.
vbk
>
> Craig McClanahan
>>
>> Jan
>>
>>>>
>>>> Jan
>>>>
>>>>
>>>>>
>>>>> vbk
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>