I have been following along the thread silently trying to finally "get" the picture.
At this point, the only reasonable question that I can ask is, if it is possible to consider providing the continuation capabilities within the Actions instead of promoting JavaScript as another language supported by Cocoon. My reasoning is that for the size and scalability of the web applications that I am dealing with, I wouldn't bet too much on a loosely typed and non-compiled language. If provided, however, I may seriously consider using a more sophisticated paradigm for flow control within my actions. I hope to learn more from this thread. Cheers, Ivelin ----- Original Message ----- From: "Simon Price" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, September 09, 2002 4:27 PM Subject: Re: [control flow] changes and new sample > I'm a newcomer to cocoon, but would be inclined to agree with Stefano > that flows are more generalised concept than an mvc controller. There > are ways of using flows that have very little to do with mvc. So, > assuming anyone can vote on these things :-) +1 for map:flow > > Simon > > > > > I vote for <map:flow>. > > > > > > > -- > > ------------------------------------------------------------------- > Simon Price > Institute for Learning and Research Technology > University of Bristol > 8-10 Berkeley Square > Bristol BS8 1HH > United Kingdom > > Direct: +44 (0)7071 226 720 > Office: +44 (0)117 928 7193 > Fax: +44 (0)117 928 7112 > [EMAIL PROTECTED] > http://www.ilrt.bristol.ac.uk > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
