Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 79889 invoked by uid 500); 17 Jun 2002 12:56:11 -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 79878 invoked from network); 17 Jun 2002 12:56:10 -0000 Message-ID: <3D0DDA47.2010408@apache.org> Date: Mon, 17 Jun 2002 07:47:03 -0500 From: Ivelin Ivanov User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.0) Gecko/20020530 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: [RT] Flowmaps 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 Reinhard Poetz wrote: > > +10 > very important because I think that many people (and me too) don't like XSPs I'm not an XSP fan either. > >>Now, suppose we do this >> >> callPipeline("hello.html", input, output); >> >>where we mean: >> >> 1) call the internal "hello.html" URI connecting the input and output >>that I give you. >> 2) come back here without sending anything to the client > > > +1 > > and ... > with the same concept we can implement validation in XMLForms if you need > access to your backend for this purpose because xml-schemes are not powerful > enough > (e.g. a customer wants to book a hotel room and you have to check before > confirming the reservation whether the room is still available) Can you elaborate some more on this idea. I didn't undertand Stefano's thought on input/output either. It appeared that the function was recursively calling the pipeline which called the function in the first place. -- -= Ivelin =- --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org