Shirish, I'm not knocking the "workflow" concept, my only point earlier was that someone shouldn't think it provides any real difference from session storage except that it will attempt to automatically clear the session when they leave that "workflow" and they won't have to put that logic in.
It's a good idea, but this latest message indicates that it limits its use to applications that only allow a single "workflow" at a time. I've worked on many applications where there may be two or three valid workflows open for a user at once, for example a help desk application where the operator may be working on one issue and then need to open a new issue (in a new window) for an incoming call in the middle of the current workflow, they are both valid and neither contains "stale" data. -Rob -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, February 12, 2004 10:50 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: [OT] - Request against Session <snip> If the user has multiple windows open all sharing a session and does different things in different windows things get really fun. </snip> If user has different windows in different windows, then only the latest windows workflow is honoured.SO all other window will have lost thier workflow state if any...Which is desired behaviour in workflow like situations...Where you dont want user to have multiple windows open and accidently submit an old window with stale data thinking he was working with the latest data... But you are right in the sense that all such stuff should go in framework... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
