At 09:11 PM 12/9/2004, Curt Arnold wrote:
The most obvious is when resolving the URL is slow or flaky. Parsing only
once avoids the dual network/floppy disk drive hit and avoids having to
deal with scenarios where the first pass succeeds and the second pass
fails due to a network or server problem. Under normal circumstances, I
don't think you would ever notice the difference but the replay approach
is simpler and has to be faster which is a win-win situation in my book.
I agree with most of your comments and also prefer the replay
approach. Having said that, the replay approach is not simpler, it
might certainly be better, but not simpler. The two passes approach is
dumb with all the advantages that go with unsophisticated solutions.
One case where the replay approach will blow the two passes approach
out of the water is when the config file has to be parsed again and
again in rapid successions. Although this does not happen currently,
it will happen as Paul makes progress with his MultiplexAppender.
On Dec 9, 2004, at 12:39 PM, Ceki G�lc� wrote:
Curt,
I has another look at the changes you posted with bug #32478 and will be
studying it closely tomorrow. I was wondering if you could think of a
use case where replaying the events would be of a significant
advantage as compared to the two passes approach. Anyway, I very much
like the idea of replaying the events and intend to commit your code
there aren't any hiccups that surface at the last minute.
--
Ceki G�lc�
The complete log4j manual: http://qos.ch/log4j/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
