> Be careful that the problem might not just be having 2 flows at a time for the > same session but also managing interrupted flows. I think allowing one flow interrupted by another will introduce lots of complexity and consume more resources. I don't think our users need it, so I don't want to overkill. If a new flow starts, we will just simply clear the existing flow.
> I don't know much of T5 internals: is the persistence strategy system > so different from T4? I start to use Tapestry since T5, so I don't know the difference. But I guess it's similar. Basically you could choose the session strategy, flash strategy or client strategy. Also fields annotated as ApplicationState are shared by all pages. You could find more information in the T5 guide. Cheers, Jeffrey Ai Martino Piccinato wrote: > > This is exactly what I'm trying to do for T4, it should be quite > inobstrusive so that conversational persistence could be added without > much effort and be easily used with your pattern if needed. Be careful > that the problem might not just be having 2 flows at a time for the > same session but also managing interrupted flows. > I don't know much of T5 internals: is the persistence strategy system > so different from T4? > > As far as I can see (am I wrong?) there's nothing in your webflow > pattern that couldn't be also done in a T4 application as it does not > imply any new feature so I think I could test everything in T4 > > Martino > > On Dec 24, 2007 8:25 PM, jeffrey ai <[EMAIL PROTECTED]> wrote: >> >> You are right. >> So far, I think our system will only support one flow at a time. This >> will >> not only make design simpler, but also save some server resource. If a >> system needs to support multiple flows, it needs a way to identify >> different >> flows in one session. >> >> Cheers, >> Jeffrey Ai >> >> >> >> Martino Piccinato wrote: >> > >> > Hi, >> > >> > I think the only thing missing is a "conversational" type of >> > persistence. That is that the application state object and persisted >> > link shouldn't be simply session persisted but at least session >> > persisted with some kind of "flowkey" prefix so to separate different >> > flows. This would imply also some flow/conversation control mechanism >> > (start/restart/reset/getFlowKey) I was planning to do a similar thing >> > for T4. >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/T5%3A-A-web-flow-idea-on-T5-tp14442158p14490669.html >> >> Sent from the Tapestry - User mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/T5%3A-A-web-flow-idea-on-T5-tp14442158p14516419.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
