logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 28647] - Add "Flush on Level" capability to FileAppender
Date Thu, 06 May 2004 03:41:51 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=28647>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=28647

Add "Flush on Level" capability to FileAppender





------- Additional Comments From paul.smith@lawlex.com.au  2004-05-06 03:41 -------
You are of course correct... When I looked in the Hierachy view within Eclipse, 
I keep seeing AppenderSkeleton, and forget that there is actually an interface.

Silly me, particularly as a log4j-dev member... 8-|

Anyway. I was thinking that the appender that is wrapped need not have extend 
from WriterAppender.  The Wrapping appender (FlushAppender in our example) is 
free to determine when to 'flush', which really means 'take any currently 
buffered events and send them to the wrapped appender'.  

This is more a more generic flushing solution but kind of duplicates the work 
that WriterAppender would do.  I guess you could have a FlushingWriterAppender 
wrapper that is only designed to wrap a WriterAppender only, and rather than 
store it's own buffer of events, always writes the event to the internal 
WriterAppender, but waits until the internal strategy determines that a flush 
should occur, and only at that point calls writerAppender.flush().

Does that make sense?

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message