For systems consisting of thousands and possibly even tens of thousands of
classes,
are there scalability advantages to naming loggers by their package name
only,
as opposed to scoping completely down to the class name? (Specifically
referring to
the Logger.getLogger(a.b.class); call.)
I'm
Message-
From: Lutz Michael [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 17, 2003 11:10 AM
To: 'Log4J Users List'
Subject: Scalability: Seeking advice on logger names
For systems consisting of thousands and possibly even tens of thousands
of
classes,
are there scalability advantages
Users List'
Subject: Scalability: Seeking advice on logger names
For systems consisting of thousands and possibly even tens of thousands of
classes,
are there scalability advantages to naming loggers by their package name
only,
as opposed to scoping completely down to the class name
[mailto:[EMAIL PROTECTED]]
Sent: Friday, January 17, 2003 11:17 AM
To: Log4J Users List
Subject: RE: Scalability: Seeking advice on logger names
Howdy,
We have systems with thousands of classes, each having a private static
final Logger with its name as the full class name. We haven't run
Howdy,
Sorry, my intent wasn't to recommend a change in the naming convention
in
general or start controversy.
Don't worry, I didn't interpret it as such ;) Just explaining some of
our (and by our I mean the projects I work on, not the log4j developer
community) design and experiences in this
