Torsten Curdt wrote:
and find that the old doc (at new URL:
http://wiki.apache.org/cocoon/GeneralizedFlow, ever so unreadable as
back then) still holds some ideas worth considering, no?
...forgotten gems :) Definitely!
I have to read up on this.
just ask for clarification if the doc
Vadim Gritsenko wrote:
Torsten Curdt wrote:
IMHO having map:act *and* map:call is not really nice.
Why not? IMHO it is more readable to have
map:act function=foo/
map:call function=bar/
than:
map:call action=my-action function=function-name/
map:call flow=my-flow
Sylvain Wallez wrote:
Torsten Curdt wrote:
Gang,
there are a few things regarding the current flow machinery that
are bugging me for quite a while now. In order to support flow
serialization they need to be addressed.
1. Class vs Interface
The WebContinuation is currently a class.
and find that the old doc (at new URL:
http://wiki.apache.org/cocoon/GeneralizedFlow, ever so unreadable as
back then) still holds some ideas worth considering, no?
...forgotten gems :) Definitely!
I have to read up on this.
for one: the possibility to have more then one 'flowEngine' as you
Torsten Curdt wrote:
3. Continuation Management
When it comes down to serialization of flow there are 2 aspects.
One is flow persistence and the other one is flow replication
across machines.
In order support flow persistence we would need the make the
ContinuationManager save and reload
Torsten Curdt wrote:
...
One of the points of the wiki page was appealing on the first glance
and turned into another RT: it might be a good idea to remove the
stigmata from actions and join the concepts a bit more. IMHO having
map:act *and* map:call is not really nice.
map:call
Gang,
there are a few things regarding the current flow machinery that
are bugging me for quite a while now. In order to support flow
serialization they need to be addressed.
1. Class vs Interface
The WebContinuation is currently a class. IMO it makes much more
sense to turn it into an
Torsten Curdt wrote:
Gang,
there are a few things regarding the current flow machinery that
are bugging me for quite a while now. In order to support flow
serialization they need to be addressed.
1. Class vs Interface
The WebContinuation is currently a class. IMO it makes much more
sense to
Torsten Curdt wrote:
Gang,
there are a few things regarding the current flow machinery that
are bugging me for quite a while now. In order to support flow
serialization they need to be addressed.
1. Class vs Interface
The WebContinuation is currently a class. IMO it makes much more
sense to
