Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 41035 invoked from network); 16 Apr 2004 14:13:04 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 16 Apr 2004 14:13:04 -0000 Received: (qmail 57530 invoked by uid 500); 16 Apr 2004 14:12:41 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 57452 invoked by uid 500); 16 Apr 2004 14:12:41 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 57406 invoked from network); 16 Apr 2004 14:12:40 -0000 Received: from unknown (HELO exchange.sun.com) (192.18.33.10) by daedalus.apache.org with SMTP; 16 Apr 2004 14:12:40 -0000 Received: (qmail 4193 invoked by uid 50); 16 Apr 2004 14:13:28 -0000 Date: 16 Apr 2004 14:13:28 -0000 Message-ID: <20040416141328.4192.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: dev@cocoon.apache.org Cc: Subject: DO NOT REPLY [Bug 28424] - [PATCH] Allow applications access to the start and end of a request X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=28424 [PATCH] Allow applications access to the start and end of a request ------- Additional Comments From Ralph_Goers@dslextreme.com 2004-04-16 14:13 ------- I certainly don't have a problem with having multiple listeners. With multiple listeners it would be important to spell out what the contract is - i.e. they should be passive and not modify anything or if they can modify the response (not my intention of a listener but its possible) then they should be guaranteed they are called in the order they are configured, etc. With the current code one could implement a RequestListenerManager that implements RequestListener. It could be configured with RequestListeners and call them and it could specify what the contract is.