Return-Path: Delivered-To: apmail-logging-log4j-dev-archive@www.apache.org Received: (qmail 24310 invoked from network); 30 May 2010 02:32:09 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 30 May 2010 02:32:09 -0000 Received: (qmail 3671 invoked by uid 500); 30 May 2010 02:32:09 -0000 Delivered-To: apmail-logging-log4j-dev-archive@logging.apache.org Received: (qmail 3627 invoked by uid 500); 30 May 2010 02:32:09 -0000 Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Log4J Developers List" Reply-To: "Log4J Developers List" Delivered-To: mailing list log4j-dev@logging.apache.org Received: (qmail 3619 invoked by uid 99); 30 May 2010 02:32:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 30 May 2010 02:32:09 +0000 X-ASF-Spam-Status: No, hits=-1479.6 required=10.0 tests=ALL_TRUSTED,AWL X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 30 May 2010 02:32:08 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o4U2VmXs021867 for ; Sun, 30 May 2010 02:31:48 GMT Message-ID: <26342910.69151275186708425.JavaMail.jira@thor> Date: Sat, 29 May 2010 22:31:48 -0400 (EDT) From: "Scott Deboy (JIRA)" To: log4j-dev@logging.apache.org Subject: [jira] Created: (LOG4J2-38) Add receiver state notification support MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Add receiver state notification support --------------------------------------- Key: LOG4J2-38 URL: https://issues.apache.org/jira/browse/LOG4J2-38 Project: Log4j 2 Issue Type: New Feature 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 is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org For additional commands, e-mail: log4j-dev-help@logging.apache.org