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]
