Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 33717 invoked by uid 500); 21 Mar 2002 09:24:35 -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 33706 invoked from network); 21 Mar 2002 09:24:35 -0000 Mime-Version: 1.0 X-Sender: media@pop3.demon.co.uk Message-Id: In-Reply-To: <00c601c1d023$687782a0$90a4558b@vgritsenkopc> References: <00c601c1d023$687782a0$90a4558b@vgritsenkopc> Date: Wed, 20 Mar 2002 18:34:37 +0000 To: cocoon-dev@xml.apache.org From: Jeremy Quinn Subject: RE: error handling !*#%! Content-Type: text/plain; charset="us-ascii" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N At 10:25 am -0500 20/3/02, Vadim Gritsenko wrote: >> From: Jeremy Quinn [mailto:jeremy@media.demon.co.uk] >> >> At 8:59 am -0500 20/3/02, Vadim Gritsenko wrote: >> >> Thoughts ? >> > >> >PS Why do we need this double buffering in the first place (thinking >> >about serializer's buffer)? >> >> Would it not be possible to set this as a parameter on a specific >> Serializer in setup? > >Because serializers isn't SitemapModelComponent, has no setup(), hence - >no parameters. Ugh! Thanks for reminding me ;) This whole concept is a bit of a hack really is'nt it? I mean as a way of capturing errors .... Not really worth changing Serializer for .... regards Jeremy -- ___________________________________________________________________ Jeremy Quinn Karma Divers webSpace Design HyperMedia Research Centre --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org