+1
Because
- I don't think this change will hurt a lot of people. Those that are hurt just need to remove their previous custom-made trace. This would most likely only require a global search/replace or some comparable refactoring.
- common.logging has it. People using this API miss it.
- .net has it
- without it, a (proper) trace-call would look like this:
if(log.isEnabledFor(XLevel.TRACE)) log.log(XLevel.TRACE, <probably very expensive string creation>)
instead of
if(log.isTraceEnabled()) log.trace(<probably very expensive string creation>)
which is less obscuring in the code. After all we are talking about the trace-level, the finest grained default level, which means that there will be lots of lines like the above in the source! This is one of the main reason why it should be included. Readable code is important.
- I can't wait until Chainsaw and other supporting applications support the trace-level "natively".
- the existance of http://nagoya.apache.org/wiki/apachewiki.cgi?Log4JProjectPages/TraceLevel tells me that it should be included since it's obviously requested quite a lot.
- I don't want to restart any religious discussions but:
- INFO is for informational Messages like "User Foo logged in." Those would appear in ordinary log-files of applications if they are turned verbose in production.
- DEBUG is for standard development like "Received message of type <TYPE>" just to see what's going on generally.
- TRACE would probably do a hex-dump of the received message. I'm talking about lots of output here that is slowing down the execution significantly. This would be used to see what's going on in depth.
Even if this is different from other peoples view, wouldn't it be best to stop this discussion/holy war/F�rmchenkrieg once and for all by just including trace for "people like me"?
I don't really see the need for a 2/3 majority for a minor enhancement like this. If only 25% of the userbase need a feature it will be reimplemented over and over again by those 25% which isn't very productive. I understand that the API shouldn't be bloated unnecessary but trace-support doesn't add a lot of bloat at all and is significant for quite some people.
Don't get me wrong but if I had to choose right now between trace and domains I'd choose trace since I really need it while the domains just sound nice and I don't see any immediate use (for me).
How long will this vote run? Is it worth a "Trace now!"-Ribbon-Campaign? ;)
Thank you for choosing the democratic way!
Joern.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
