-----Original Message----- From: Bryan Lewis [mailto:[EMAIL PROTECTED] Sent: Saturday, May 07, 2005 1:37 PM To: Tapestry users Subject: Re: Multiple Instances of the Same Page and Persistence
I don't have an answer for you, but I came across a similar problem a few days ago with Firefox. I assume it's Firefox since you mentioned opening
<snip>
You know I'm actually not sure now that this is firefox related. I fired up my copy of IE (6.0.29), logged into my app, then did:
File->New Window ... Used Same Session as old window Right Click Link-> Open in new window ... Used same session as old window
This has always been the case, there is nothing preventing the browser from opening several views to a server using the same session. Otherwise how would for example pop-up windows work?
You have to take this into consideration no matter what web-framework you use. If you think about it this is comes from the fact that HTTP is a stateless protocol. Someone once described it as a fax-protocol. The webserver sends a fax with the page - say an order form. The browser faxes the users order (POST) to the server.
The server really has no clue which order-form the user looked at when posting the data to the server. The page might not even have anything to do with the page flow the programmer assumed, there is alweays the back button, bookmarks, cached information, several windows and so on.
The best you can do is to try to detect that the information the browser POSTs to the server is old and the user needs to see a fresh order form. This is what Tapestry uses the rewind and stale link messages to tell the user.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
