I'm interested in this as well. Specifically if a user has two page instances open, how can T5 persistence be used reliably?
I found on Safari and Firefox (not sure about IE, but likely a problem there as well) that the persisted session properties are shared between page instances and each page can overwrite the another. My searches didn't come up with a definitive answer although I did see that the question has been asked several times. Can anyone comment on this or provide a workaround? Peter Stavrinides wrote: > > ... but what would be ideal in my humble view is a proper page persistence > Strategy, where a value is retained until the user leaves the page. In > truth someone posted such a solution which used a cookie, and it seemed to > behave exactly as it should, nevertheless I am still against relying on a > cookie. I understand this may be difficult to implement due to Tapestry's > inner workings, particularly the way pages are pooled, but since > conversational state covers some of this ground (the difference being a > conversation is tied to not only the page, but the window so each tab is > treated as a new conversation)... > -- View this message in context: http://www.nabble.com/Persistance-tp20732003p20743522.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]
