Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Date: Thu, 26 Feb 2004 08:49:01 +0100
Subject: Re: Flowscript and return to pipeline
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Mime-Version: 1.0 (Apple Message framework v553)
From: Bertrand Delacretaz <bdelacretaz@apache.org>
To: dev@cocoon.apache.org
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <31DF72A980E5D511B48C000102BD8685061DB235@calexc01.diginsite.com>
Message-Id: <3DFB77E0-6830-11D8-8E8F-000393CFE402@apache.org>

Le Jeudi, 26 f=E9v 2004, =E0 01:14 Europe/Zurich, Ralph Goers a =E9crit =
:

> ...I have no problem with using flowscript to
> manage a couple of pages that are linked together  (i.e. - a form to=20=

> fill
> out followed by a confirmation page). But using it for more than this
> violates the separation of concerns principal that Cocoon strives to=20=

> achieve
> through the sitemap. It is far too easy to start throwing all your=20
> business
> as well as presentation logic into flowscript and soon you'll end up=20=

> with
> something worse than JSPs....

Agreed - but many powerful tools can be abused or dangerous if you=20
don't play by the rules. Take a fast motorbike for example, Flow might=20=

be our V-Max currently ;-)

I think we're still exploring the many avenues that Flow opens, and,=20
after some time, we'll know what to use and what not to use. But=20
prematurely limiting options would prevent us from going forward.

-Bertrand

[1] http://www.biketown.co.uk/Bike_Reviews/Yamaha/VMax/VMax.html