[logback-user] SiftingAppender and RollingFileAppender, roll on close.

Becker, Thomas Thomas.Becker at netapp.com
Sat Apr 13 02:01:08 CEST 2013

There was already a Map there.  To your point though, that bit of rework to AppenderTrackerImpl was not strictly necessary but I felt the existing code, which essentially re-implemented LinkedHashMap in a clumsy way was  pretty low hanging fruit.  I'd be willing to make additional changes if the maintainer showed interest in accepting the patch, but my immediate need has passed.  My observation has been that the majority of the pull requests to Logback seem to get no comments at all.  But I went ahead and reopened this one here: https://github.com/qos-ch/logback/pull/107


From: Logback-user [logback-user-bounces at qos.ch] on behalf of diroussel [nabble at diroussel.xsmail.com]
Sent: Friday, April 12, 2013 12:12 PM
To: logback-user at qos.ch
Subject: Re: [logback-user] SiftingAppender and RollingFileAppender,    roll on close.


That functionality looks good.

In order to get accepted, maybe you can make your changes to
AppenderTrackerImpl less invasive?

In AppenderTrackerImpl, you are subclassing LinkedHashMap instead of using
ch.qos.logback.classic.pattern.LRUCache.  But really there is no need for a
map. Just keep the existing head and tail references, keep a count
variablle. If the count gets to high, then remove entries from the tail.

I like that you've added unit tests and the code formatting is consistent
with the rest of the code base.


View this message in context: http://logback.10977.n7.nabble.com/SiftingAppender-and-RollingFileAppender-roll-on-close-tp11840p11862.html
Sent from the Users mailing list archive at Nabble.com.
Logback-user mailing list
Logback-user at qos.ch

More information about the Logback-user mailing list