Problem is, WWW has a very dim view on what a window is. Sometimes it can have a kind of id (with javascript):
But if the user clones a window I suppose this id will be duplicated?<A HREF="/public/Details/2451819_1.html" TARGET = "_new" onClick="wind +ow.open('/public/Details/2451819_1.html','600175392813981','height=17 +5,width=300,scrollbars=1,alwaysRaised=1,resizable=1');return false">
When the application through the user's action changes state, the application should check that this state change is possible.
Part of the information for that might come from the session object, where there could e.g. be a different sort order preference for different windows.
One solution could be to give new
hidden field/cookie/mangled path
for each new action the user takes, or state he puts the application in. Yeah, that's probably the way to go:
Make changes to the session object to reflect new state and bind the updated object (and hence the state) to a new session id.Wreaks havoc with the "back" button though.
But what happens to old rogue windows with old rogue session objects, could they nullify state changes if the user makes actions from them? I suppose this depends on the state change handling on the server side. If one is careful to code what data affects the user interface only and what parts actually do transactions that may be enough.
/jeorgen
In reply to Re: practical aspects of sessions and state
by jeorgen
in thread practical aspects of sessions and state
by d_i_r_t_y
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |