At 09:33 PM 1/12/2006, Scott Deboy wrote:
General SLF4j concern:
I may be in the minority (I'm sure I am), but slf4j's change to require
logger.debug(string) instead of object may have a performance rationale
but it has the effect of preventing filters from being able to perform any
analysis
The recent changes (r 369909 and 369913) added optimization for
single argument format requests that satisfy the threshold
requirements. If the pattern contains quotes or substitution tokens
other than {0}, the request will be delegated to
java.util.MessageFormat, otherwise it will be
|
| One of my concerns was introducing yet another pattern syntax when Java class
| libraries already have two (java.text.MessageFormat and java.util.Formatter).
| I had originally thought that the substitution pattern format was a subset of
| that supported by java.text.MessageFormat,
same
At 07:51 AM 1/12/2006, Curt Arnold wrote:
I committed a pass at external message formatting classes in the
sandbox. The code can be checked out using:
svn co http://svn.apache.org/repos/asf/logging/sandbox/log4j/ formatter
formatter
and can be built using either Maven (JDK 1.5 only) or Ant.
-Original Message-
From: Ceki Gülcü [mailto:[EMAIL PROTECTED]
Sent: Thu 1/12/2006 7:47 AM
To: Log4J Developers List
Subject: Re: Experimental log4j formatter in sandbox
At 07:51 AM 1/12/2006, Curt Arnold wrote:
I committed a pass at external message formatting classes in the
sandbox. The code
On Jan 12, 2006, at 9:47 AM, Ceki Gülcü wrote:
What is wrong with enshrining a solution that is optimized for the
task at hand by being simple, easy to use and CPU effective?
If you are providing one true way of doing something (in this case,
formatting messages for logging), then your
On Jan 12, 2006, at 9:47 AM, Ceki Gülcü wrote:
Unfortunately, SLF4J support was recently removed. I
would like to see it restored. I can personally vouch that keeping
NLOG4J in sync with SLF4J is almost effortless, especially since the
SLF4J is now quite stable. Unless there is opposition, I'd
On Thu, 2006-01-12 at 12:33 -0800, Scott Deboy wrote:
I may be in the minority (I'm sure I am), but slf4j's change to
require logger.debug(string) instead of object may have a performance
rationale
One thing I like the log4j design, was being able to log non-string
objects. I've used it
