[logback-dev] [JIRA] (LOGBACK-266) FixedWindowRollingPolicy MAX_WINDOW_SIZE too small?

[Ceki Gulcu (JIRA)]

Ceki Gulcu commented on LOGBACK-266 FixedWindowRollingPolicy MAX_WINDOW_SIZE too small? I really like your idea about not having to rename. A policy where the index is incremented by one and deleting the oldest file, would not require any file renaming. TCP is based on a similar idea called a "sliding" window. It follows that such a policy should be called SlidingWindowRollingPolicy in deference to TCP. Given that it is possible to archive logs by time and size [1], I don't see the need for FixedWindowRollingPolicy nor SlidingWindowRollingPolicy. I am tempted to mark FixedWindowRollingPolicy as deprecated by [1] and move on. Is there a use case covered by FixedWindowRollingPolicy and not SizeAndTimeBasedFNATP? I should ask on the mailing list. I'll post a message on the logback-user list asking for user opinion. Anyway, not to add more delay to the resolution of this bug, pull request 110 has been merged. [1] http://logback.qos.ch/manual/appenders.html#SizeAndTimeBasedFNATP [2] https://github.com/qos-ch/logback/pull/110

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

_______________________________________________
logback-dev mailing list
logback-dev@qos.ch
http://mailman.qos.ch/mailman/listinfo/logback-dev