I personally see TRACE as unrelated to severity, so if I were to have unlimited 
resources, I'd prefer to implement per-event attributes instead.

However, I'm not against the change because I understand there are a group of 
people who want more data points and this is the easiest way to get it.

If we decide at some point in the future to support attributes at the event 
level (MDC and NDC don't fit the bill here), I can enable an aspect-oriented 
style of logging by adding attributes describing the aspects on the event: 
'database', 'authentication', etc.

When I want to 'trace' the 'authentication' process, I enable logging for 
events with the 'authentication' attribute.

Scott





-----Original Message-----
From:   Ceki Gülcü [mailto:[EMAIL PROTECTED]
Sent:   Wed 5/18/2005 12:54 PM
To:     Log4J Developers List
Cc:     
Subject:        RE: [VOTE][RESULT] Release Overview Proposal
At 20:37 5/18/2005, you wrote:
>There seems to be fairly broad support for it.  No one voted -1 for the
>proposal.
>
>It is in addition to the constants and methods that are already there, so it
>(hopefully) meets the requirement of not being harmful to existing
>deployments.  Developers that have extended to support trace may have
>issues, but they can stay at 1.2.11 until they are ready to take the plunge
>with 1.2.12 or 1.3.
>
>I guess, define "everyone" for me.

I'd lean against adding the TRACE level to the 1.2 branch. Scott and Jake 
may feel the same way. In my opinion, the TRACE level promotes bad habits, 
especially in light of the confusion between  TRACE and DEBUG. There is 
also the question of backward compatibility over the wire. If TRACE was 
introduced in 1.2.11 it would be incompatible with versions 1.2.9 and earlier.




-- 
Ceki Gülcü

   The complete log4j manual: http://www.qos.ch/log4j/



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




<<winmail.dat>>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to