|
From: Seth L. <set...@gm...> - 2005-04-01 00:55:58
|
On Thu, 31 Mar 2005 19:46:42 -0500, Keith Donald <ke...@in...> wrote:
> Seth,
>
> Excellent idea.
>
> If we extract an interface from the HttpServletExecutionManager, we get
> something like:
>
> public interface FlowExecutionStorage {
> public FlowExecution loadFrom(Event inputEvent);
> public void saveOrUpdate(FlowExecution flowExecution);
> public void remove(FlowExecution flowExecution);
> }
>
> Or something like that. Erwin what do you think? Need to think about it
> more. I imagine here the FlowExecutionStack would have to be reconstructed
> from the Event parameters, for example: http request parameters, in an http
> servlet environment. It also has to be rehydrated with services on
> deserialization as well, including the FlowLocator and its
> FlowExecutionListenerList.
Keith,
Just so I'm clear... this isn't to replace the concept and purpose of
the HttpSession? This is just to provide a way to get the state info
of the flow into the request to avoid the need for session creation?
Thanks!
Seth
|