Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 16283 invoked by uid 500); 20 Mar 2002 13:47:30 -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 16251 invoked from network); 20 Mar 2002 13:47:30 -0000 Mime-Version: 1.0 X-Sender: media@pop3.demon.co.uk Message-Id: In-Reply-To: <004d01c1d00d$f15c39f0$670004c0@PC103> References: <006701c1cf2d$ffc827f0$670004c0@PC103> <026301c1cf49$9db98d30$670004c0@PC103> <004d01c1d00d$f15c39f0$670004c0@PC103> Date: Wed, 20 Mar 2002 13:46:04 +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 1:51 pm +0100 20/3/02, Nicola Ken Barozzi wrote: >From: "Jeremy Quinn" > >The request processing should be done (and usually is) with objects rather >than in the pipeline. Incedentally, (apart from the issue of error handling) if I am using bad patterns for developing webapps, I would be grateful if someone points this out. will inevitably be used as an example for how to do this sort of thing (that is the intention anyway). If the patterns I am using are bad, it would not be good to promote them. 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