[logback-dev] [JIRA] Resolved: (LBCORE-93) FlushingPolicy

Ceki Gulcu (JIRA) noreply-jira at qos.ch
Thu Mar 18 18:33:16 CET 2010


     [ http://jira.qos.ch/browse/LBCORE-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ceki Gulcu resolved LBCORE-93.
------------------------------

    Resolution: Won't Fix

Flushing is not critical to performance.

> FlushingPolicy
> --------------
>
>                 Key: LBCORE-93
>                 URL: http://jira.qos.ch/browse/LBCORE-93
>             Project: logback-core
>          Issue Type: New Feature
>            Reporter: Ceki Gulcu
>            Assignee: Ceki Gulcu
>
> Let flushing be a settable policy of WriteAppender. Thus, the user would be able to set the FlushingPolicy of a WriterAppender or any
> derived class which would allow you to flush the underlying output stream according to any criteria available to the shouldFlush() method
> (see below), including time.
> Here is the relevant interface:
> interface FlushingPolicy {
>    booelan shouldFlush(LoggingEvent e);
> } 
> We could easily imagine a policy flushing on every warning or error in addition to special markers. For example,
> Marker FLUSH = MarkerFactory.getMarker("FLUSH");
> logger.info(FLUSH, "finished serving request {}", request.getId()); 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the logback-dev mailing list