Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
From: "Andrzej Jan Taramina" <andrzej@chaeron.com>
Organization: Chaeron Corporation
To: Sylvain Wallez <sylvain@apache.org>
Date: Sun, 09 Nov 2003 21:20:15 -0500
MIME-Version: 1.0
Subject: Re: Saving pipeline output to a temp file...everything you wanted to
 know but were afraid to ask!
Reply-to: andrzej@chaeron.com
CC: dev@cocoon.apache.org
Message-ID: <3FAEAF8F.2594.59278C@localhost>
Priority: normal
In-reply-to: <3FA95C24.8050506@apache.org>
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body

> That's why I'm suggesting an action of type "flowscript" that would call a
> function defined in the script files listed in <map:flow> and thus be able to
> share the session-global variables with <map:call> statements. Think of this
> action as a "secondary controller" in a MVC model (they fine-tune the view but
> don't change it radically), the <map:call> being the primary controller (it
> chooses the pipeline URI that fully defines the view).

So long as you clearly document the new way of doing this, and leave the old 
way in place for at least one release cycle!

Mind you, given the state of Cocoon docs, that is a lot to ask, non?  ;-)

Keep in mind that my application will be used by over 10K users at a huge 
brokerage firm....so breaking the current behaviour (even if it was not 
intended) would not be a "good thing" for Cocoon's reputation in the 
industry.

Thanks.


Andrzej Jan Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com