Re: Use of flowscript

[Ugo Cei <u....@cbim.it>]

Reinhard Poetz wrote:
> From: Tim Olson
>>flow scripts seem to present the same problem as ASPs, JSPs, and 
>>XSPs in
>>that too much process logic ends up on the web server, 
>>disjoined from the business objects they work with.  granted, 
>>if you write them correctly they are simple, but i've never 
>>seen this in practice.  it's too tempting for someone to put 
>>code in the view layer to just "get it done"
> I don't understand this. Of course every technology can be abused (IMHO
> actions are the best candiate to be abused BTW) but from the mentioned
> technologies (including actions) flowscript is the technology that
> prevents you best from abuseing it.

Abusing the flowscript might come in handy. You can do a quick 
javascript prototype of your logic, test it, then refactor it in Java. 
This is what we do all the time here.

	Ugo

-- 
Ugo Cei - Consorzio di Bioingegneria e Informatica Medica
P.le Volontari del Sangue, 2 - 27100 Pavia - Italy
Phone: +39.0382.525100 - E-mail: u.cei@cbim.it

RE: Use of flowscript

[Reinhard Poetz <re...@apache.org>]

> -----Original Message-----
> From: Ugo Cei [mailto:u.cei@cbim.it] 
> Sent: Wednesday, September 24, 2003 12:32 PM
> To: dev@cocoon.apache.org
> Subject: Re: Use of flowscript
> 
> 
> Reinhard Poetz wrote:
> > From: Tim Olson
> >>flow scripts seem to present the same problem as ASPs, JSPs, and
> >>XSPs in
> >>that too much process logic ends up on the web server, 
> >>disjoined from the business objects they work with.  granted, 
> >>if you write them correctly they are simple, but i've never 
> >>seen this in practice.  it's too tempting for someone to put 
> >>code in the view layer to just "get it done"
> > I don't understand this. Of course every technology can be abused 
> > (IMHO actions are the best candiate to be abused BTW) but from the 
> > mentioned technologies (including actions) flowscript is the 
> > technology that prevents you best from abuseing it.
> 
> Abusing the flowscript might come in handy. You can do a quick 
> javascript prototype of your logic, test it, then refactor it 
> in Java. 
> This is what we do all the time here.

Yep, I do the same with the business logic (first JS then Java). What I
haven't understood is "it's too tempting for someone to put 
code in the view layer to just 'get it done'".

Reinhard