Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 34682 invoked by uid 500); 17 Jun 2002 19:35:19 -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 34607 invoked from network); 17 Jun 2002 19:35:18 -0000 Message-ID: <3D0DB77D.7980C1A8@apache.org> Date: Mon, 17 Jun 2002 12:18:37 +0200 From: Stefano Mazzocchi X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: [RT] Flowmaps References: <3D0CB445.6D832A1C@apache.org> <1024262645.2523.123.camel@rammstein> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Bruno Dumon wrote: > > On Sun, 2002-06-16 at 17:52, Stefano Mazzocchi wrote: > [snip] > > > > [NOTE: it is *not* required that you use continuations for your flow > > logic, you can use whatever means you have to control state as you did > > previously, such as REST-like passing style, sessions or cookies] > > > > You state that "it is *not* required that you use continuations". > Suppose that I choose not to, then what advantage do flowmaps provide > over actions? I see mostly a big one: try/fail cycle is reduced by orders of magnitude with actions, you have to compile the java, move the class, restart cocoon (if not the servlet container, in some cases) and retry. I personally see others, but the above is the only big objective one I can think of. -- Stefano Mazzocchi One must still have chaos in oneself to be able to give birth to a dancing star. Friedrich Nietzsche -------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org