Delivered-To: cgu@qos.ch
Subject:
Date: Thu, 5 Jul 2001 20:37:49 -0700
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Index: AcEFy5fxEkmkMnCjEdWriwAIx78wWg==
From: "Nathan Brown" <nbrown NOSPAM thystonius.com>
To: <java-logging-input@eng.sun.com>

Sun Java Logging Folks,
In support of the Apache log4j project, I'd like to send you my request
to reconsider your proposed standard for a logging API.  Having
experience with log4j and with JSR47, I can say that my clients and I
have had much better experiences using the log4j libraries.  As has been
pointed out many times,  these libraries are very similar however, to
me, the most important aspect of log4j is the style of configuration and
flexibility.  Using XML configuration documents, multiple handlers, and
a variety of output formats gives log4j it's strength and appeal.
Java stands for many things, but to me, it represents "flexibility".
The Java API doesn't close doors, it opens them, and I find it
disappointing to see a knowingly sub-standard package make it into the
API when a more flexible and robust library exists.

Nathan Brown
R & D Manager
Chirp Productions