All I am saying is that the Ctrl-N is not a *special* case. Having 2 browsers is no different from having a single browser because on a single browser, you have the "Back" and "Refresh" buttons.
In other words, whatever problems you have with multiple browsers, I can create the exact problem using a single browser. As to solve the problems, techniques like: - state machine - workflow management - token synchronisation - etc are used to handle (sorry I used prevent in my previous mail. It's not the right word) "Back" and "Refresh" buttons from the serverside (very important to note that it's not the client-side). Keith -----Original Message----- From: Jorge Ruiz (SX) [mailto:[EMAIL PROTECTED]] Sent: Friday, 25 January 2002 2:27 p.m. To: Struts Users Mailing List Subject: Re: Session in multiple windows on same machine > My conclusion is if you have designed your application to handle the "Back" > and "Refresh" buttons, then you have inherently solved the Ctrl-N problem. How could you possibly do that? HTTP protocol has no way to tell the difference from a first GET, ot the GET from a refresh. I have the same problem: how to have two different sessions of the same application (or even different applications) in the same computer via two browser windows? This is an interesting issue. Any help highly appreciated. Jorge ----- Original Message ----- From: "Keith Chew" <[EMAIL PROTECTED]> To: "Struts Users Mailing List" <[EMAIL PROTECTED]> Sent: Thursday, January 24, 2002 3:53 PM Subject: RE: Session in multiple windows on same machine > Hi > > Let's start on url-rewriting. When you open a browser, eg > http://localhost/page1.jsp;jsessionid=1111111 > > All the browser has is the session id, right? > > Now, clicking on Ctrl-N (new window) is no different from clicking on > Refresh. Let's assume you did a Ctrl-N, you now have 2 windows. Ok, using > the window 2, you browse to another link: > http://localhost/page2.jsp;jsessionid=1111111 > > That goes ok. Now in window 1, you click on another link: > http://localhost/page3.jsp;jsessionid=1111111 > > There's no different from typing the link on window 2. > > My conclusion is if you have designed your application to handle the "Back" > and "Refresh" buttons, then you have inherently solved the Ctrl-N problem. > > When you use cookies, it's another story. If the browser shares the same > cookie (the equivalent of the url-rewrite example above), then you are ok. > > My 0.2 cents > Keith > > > -----Original Message----- > From: Sahni, Ishtmeet [mailto:[EMAIL PROTECTED]] > Sent: Friday, 25 January 2002 9:44 a.m. > To: Struts Users Mailing List (E-mail) > Subject: Session in multiple windows on same machine > > > Hi, > I am using a singlr form bean for a couple of HTTP requests. This form bean > has a session scope. As the session is related to a user through cookie or > URL rewriting what happens if a user opens another instance of application > (using open new window in browser) from existing instane. As the cookie is > same do both instances of application share same session. If so what are > the ways to avoid two instances of browser sharing a session as it can cause > synchronisation problems > Thanks > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
