Re: [Springframework-developer] SWF - Creating HTTP sessions - Feedback needed

[Erwin V. <erw...@er...>]

The storage interface doesn't need to worry about scoping: it only needs to 
deal with flow scope. Request scope and event scope never outlive the 
current request.

Erwin Vervaet
----- Original Message ----- 
From: "Rob Harrop" <ro...@ca...>
To: <spr...@li...>
Sent: Friday, April 01, 2005 11:00 AM
Subject: Re: [Springframework-developer] SWF - Creating HTTP sessions - 
Feedback needed


> What about scoping - how will this be handled by the storage interface?
>
> Rob
>
> Keith Donald wrote:
>
>>Yes, so a HttpSessionFlowExecutionStorage would use the HttpSession, a
>>HttpRequestFlowExecutionStorage would use the request, for example.  The
>>latter would also have to know how to reconstruct the FlowExecution soley
>>from the request parameters, while the former would just pull an existing
>>instance from the HttpSession given the flowExecutionId in the input 
>>Event.
>>
>>Keith
>>
>>-----Original Message-----
>>From: spr...@li...
>>[mailto:spr...@li...] On Behalf 
>>Of
>>Seth Ladd
>>Sent: Thursday, March 31, 2005 7:56 PM
>>To: spr...@li...
>>Subject: Re: [Springframework-developer] SWF - Creating HTTP sessions -
>>Feedback needed
>>
>>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
>>
>>
>>-------------------------------------------------------
>>This SF.net email is sponsored by Demarc:
>>A global provider of Threat Management Solutions.
>>Download our HomeAdmin security software for free today!
>>http://www.demarc.com/info/Sentarus/hamr30
>>_______________________________________________
>>Springframework-developer mailing list
>>Spr...@li...
>>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>
>>
>>
>>-------------------------------------------------------
>>This SF.net email is sponsored by Demarc:
>>A global provider of Threat Management Solutions.
>>Download our HomeAdmin security software for free today!
>>http://www.demarc.com/info/Sentarus/hamr30
>>_______________________________________________
>>Springframework-developer mailing list
>>Spr...@li...
>>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>
>>
>>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by Demarc:
> A global provider of Threat Management Solutions.
> Download our HomeAdmin security software for free today!
> http://www.demarc.com/info/Sentarus/hamr30
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>