Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Message-ID: <42AEDFB6.1000506@dslextreme.com>
Date: Tue, 14 Jun 2005 06:46:30 -0700
From: Ralph Goers <Ralph.Goers@dslextreme.com>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: Small dilemma: are Actions still recommended?
References: <44D253D9-9556-4570-BC54-FABCB8370556@hard-bop.com>
 <42ADFE43.8080204@apache.org>
In-Reply-To: <42ADFE43.8080204@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Sylvain Wallez wrote:

> Glen Ezkovich wrote:
>
>> Cocooners,
>>
>> Working on some introductory documentation I ran into a slight  
>> dilemma. I want to mention how Cocoon is able to access either the  
>> model or a database in response to a request and produce a response  
>> based on the result. Because of its simplicity, I will be  
>> concentrating on JSFlow in this particular document. All my Actions  
>> have been converted to flowscripts. I'm unsure of the communities  
>> perspective. So, are Actions still recommended as a way to access 
>> and  process data?
>
>
>
> No. The current use of actions as I see it is for small 
> general-purpose things, but not for application-level processing, 
> which should be orchestrated by the flow engine (be it flowscript of 
> javaflow)
>
> Sylvain
>
Maybe so, but I'd never deprecate them.  They are still highly useful.