Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 57008 invoked by uid 500); 6 Jan 2002 16:47:27 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 56997 invoked from network); 6 Jan 2002 16:47:27 -0000 Message-ID: <3C388005.4030509@anyware-tech.com> Date: Sun, 06 Jan 2002 17:49:09 +0100 From: Sylvain Wallez Organization: Anyware Technologies User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.7) Gecko/20011221 X-Accept-Language: fr, en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: Allowed Sitemap Constructs References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N John Morrison wrote: >>Agreed. -1 as well. Well, until somebody comes up with the need for an >>action to be executed *after* a serializer. >> > >How about this one: if the serializer doesn't throw an exception then >you *know(?)* the client recieved the request. An action after >serialization maybe to log the fact that they got it perhap for usage >charging...? > >J. > Don't forget that the sitemap is a regular component (in HEAD, not in 2.0). So such accounting could be also done at Processor level : just add this feature to a subclass/wrapper of SitemapHandler (or soon TreeProcessor ?) and list that component in cocoon.xconf. Sylvain --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org