cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 28424] - [PATCH] Allow applications access to the start and end of a request
Date Fri, 16 Apr 2004 14:13:28 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=28424>.
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.

Mime
View raw message