On Sun, 2 Nov 2003, Ceki Gülcü wrote:

|
| Domains result from an *internal* refactoring of loggers. In 1.2.8 a logger
| is:
|
| 1) an object where appenders can be attached to, and
| 2) an object which can decide whether a log statement is enabled or not
|
| In the next version of log4j, a logger can be viewed as a shell around one
| or more domains, where domains are:
|
| 1) an object where appenders can be attached to, and
| 2) an object which can decide whether a log statement is enabled or not
|
| A logger just glues multiple domains together. A logger has fixed rules
| defining the interaction of the domains it contains.
|
| A hierarchy is a space where multiple domains live in a hierarchical setup.
| It can be viewed as a forrest where multiple trees (i.e. domains linked in
| a tree like structure) live.
|
| I hope this sheds some light on this topic. Much better documentation will
| become available in the near future.

Pretty much what I'd expect, but how does a Logger decide if it should log
or not? This sounds like a lot of overhead (it has to check its entire
list of attached domains? Or is there a way to "quick-return" if the
statement shouldn't log?).

And definately a 2.0 thing, this is no small refactor.

|
| Coming back to the TRACE level, I think that domains may offer a better
| alternative. The ongoing discussion has raised some very interesting
| questions to which I do not have definitive answers.

You haven't answered my post on this.

a) Performance impacts, as trace is an extremely verbose level.

b) Levels define an implicit view of the -importance- of a log-statement -
and not "where it comes from", or who should view it, as such. It's a
descriptive -importance level-. Domains wont supersede this.

c) Trace is something else!


-- 
Mvh,
Endre Stølsvik               M[+47 93054050] F[+47 51625182]
Developer @ CoreTrek AS         -  http://www.coretrek.com/
CoreTrek corporate portal / EIP -  http://www.corelets.com/

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

Reply via email to