Sylvain Wallez wrote:
>
> So what about the simple "flow.exit()"? I also though about
> "flow.kill()" but it can convey the meaning of killing the current
> continuation tree. There's also "flow.stop()" but it implies a possible
> return which is not what we want.
>
> We could also start providing flow.sendPage{AndWait}(),
> flow.sendStatus(), flow.getComponent() etc... as direct links to their
> cocoon.* counterpart and initiate the migration of their implementation
> from FOM_Cocoon to a new FOM_Flow without backward incompatibility.
>
> WDYT?
>
+1
Carsten
--
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/
