Pipeline Component Client/Svr State Mgt

[Paul Havey <pa...@yahoo.com>]

I was looking at the turbine pipeline pattern.
 
Id like to know whether the API simply executes the
pipeline atomically or allows components to send a
response be put into a wait state (save context to
session), then on next post start execution from next
component... bypassing all previous components... That
way u could have a wizard type screen... sending
information back n forth thruout the lifetime of the
pipeline processing...

Also it would be nice to have a decision making
component that conditionally branches off to one of  a
possible number of components... These components
would be in the xml descriptor but the condition may
be undescribable here...

U may also want to fire off a pipeline from a
pipeline... reusing pipelines... and have global
pipelines that are executed for every request (as in
authentication) it is cumbersome to have to specify
these for every action... although ud then have to
have the ability to turn it off for an action...

Im a newbie to all this but I think with this
functionality the pipeline model answers all questions
in terms of extensibility... let me know how I can
help...



__________________________________________________
Do You Yahoo!?
Yahoo! Autos - Get free new car price quotes
http://autos.yahoo.com

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>