multiple client windows & persistent page properties

[Miles Egan <mi...@caddr.com>]

I have an application that uses persistent page properties to store an object so 
the user can make a series of edits to the same object.  This all works great 
until a user tries to use the page to edit two different objects in the same 
session.  For instance, a user loads object a into a browser window, then loads 
object b into another window or tab of the same browser.  Then then go make an 
edit to object a in the first window but the changes are written to object b 
because it was the last object loaded into the form.  Needless to say this makes 
people very unhappy.  Is there a simple way to get around this problem?  A 
not-so-simple way?

miles

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org