You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Matt Sicker (JIRA)" <ji...@apache.org> on 2014/08/28 06:03:58 UTC

[jira] [Updated] (LOG4J2-38) Add receiver state notification support

     [ https://issues.apache.org/jira/browse/LOG4J2-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Sicker updated LOG4J2-38:
------------------------------

    Component/s: Core

> Add receiver state notification support
> ---------------------------------------
>
>                 Key: LOG4J2-38
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-38
>             Project: Log4j 2
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Scott Deboy
>
> Specific scenario:
> For (VFS)LogFilePatternReceiver, setting the 'tailing' flag to true means the receiver continually tracks the current position in the file, and when the file is truncated, it would be helpful to communicate that information back to whoever initialized the receiver (in this case, users may want Chainsaw to automatically clear the log when that happened, or create a new tab, etc).
> I'm not sure if this feature can or should be generalized, but I've heard this request a number of times.
> Maybe this shouldn't be a general concept, maybe a resetableReceiver interface would suffice, and the interface would provide add/removeResetListener.  When the file is truncated, the listener would be notified.
> There is already a concept of a VisualReceiver, which allows the same VFS receiver to prompt for user login credentials, so a ResetableReceiver or some other name would be consistent with the extensions already in place to support other interactions with the app managing the receiver.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

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