|
From: Colin S. <col...@ex...> - 2005-04-01 20:12:42
|
Tapestry 3.1/4.0 (the current CVS version of Tapestry) also makes this pluggable... Storing page state in the Session is just the default. Alef Arendsen wrote: > It's what ASP.NET (and I think some JSF implementations) does as well > - serialization of the state in a hidden input field. I don't think > it'd be that difficult to implement a custom tag that does this, > wouldn't it? > > rgds, > Alef > > On Mar 31, 2005, at 10:30 PM, Rob Harrop wrote: > >> I see no problem in implictly creating a session - although I am >> concerned about the impact of this on clustered applications. Can the >> session implementation be factored out so that users can implement >> their own session storage? >> >> Rob >> >> Erwin Vervaet wrote: >> >>> The Spring Web Flow (SWF) FlowController forces the "requireSession" >>> property it inherits from AbstractController to "true". This is >>> logical since the webflow system needs to store flow execution state >>> in the HTTP session. >>> >>> So far so good. However, since the controller now requires an >>> existing session, the user/developer is responsible for creating >>> that session before a flow is started. This is typically not a >>> problem in real-life applications since those carefully manage >>> session creation and invalidation. >>> >>> Still, we are wondering whether it is a good idea to implicitly >>> create sessions (usually using request.getSession()) in a >>> controller, or should this be left as a responsability of the >>> application developer? Note that AbstractWizardFormController and >>> AbstractFormController implicitly create sessions. >>> >>> Erwin Vervaet >>> erw...@er... >> |