|
From: Seth L. <set...@gm...> - 2005-03-31 23:21:33
|
On Thu, 31 Mar 2005 17:49:24 -0500, Keith Donald <ke...@in...> wrote: > Just thinking out loud here, but no, I don't think this would be too > difficult to implement. There is potentially lot to serialize out on each > request, though, particularly if you a flow execution that has spawned many > nested subflows. > > Methinks we could have custom tag that serializes the FlowExecutionStack on > each request. This would include serializing: > - The ID of the flow execution (randomly generated guid) > - The stack of IDs of all spawned flows, the top being the active flow and > the rest any suspended parent flows (if the active flow is a subflow) > - For each flow in the stack, everything in 'flow scope'. Keith, Sounds like there might be two Strategies here for storing the FlowExecutionStack: HttpSession Strategy and HttpRequest Strategy. The developer can then choose the strategy for their needs, as there are good use cases for not requiring a session. Seth |