This is not really a struts 2 issue but a browser issue. This is the way firefox persists sessions. If you try same thing in IE6 it will work fine, IE7 some times and IE8 fully emulates firefox.
Furthermore you can try this with gmail and you will see the same behaviour. This is a fairly well known "limitation" of firefox if you want to call it a limitation, I for one think this is the correct thing to do, and since even IE8 starts doing this looks like it is. The solution for FF is to use profiles. Just google for 'Firefox multiple sessions. -----Original Message----- From: Greg Lindholm [mailto:glindh...@yahoo.com] Sent: January 19, 2009 2:19 PM To: user@struts.apache.org Subject: Re: Struts 2 session problem +1 I find I need this all the time when developing; I want to login as 2 different users and test multi-user interactions. Currently I'm forced to use 2 different browsers, login once with Firefox and once with IE. This works for development but wouldn't be an acceptable answer for users (plus many work places dictate the browser you will use and don't allow "users" to install other browsers.) Fortunately the only thing I store in the session is a Login object with user credentials and preferences etc. so this allows a user to have multiple browser windows open to the same application, they share the same session (this is the more common use case.) I have a harder time coming up with a legitimate use case for allowing an ordinary user to be logged into 2 different accounts at the same time. (I'm sure that there are legitimate cases but they are more fringe.) On the other hand, if you use "conversation scope" wizards etc. in your app I would expect a user to be able to have a separate conversation in each open window (shared session) without stomping on each other. This would mean the conversation state could not be stored in the session unless it is identified with a particular window/tab/frame etc. (a session token could be used in a hidden field). newton.dave wrote: > > dusty wrote: >> Creating a separate subsystem on the server to partition a single HTTP >> session for multiple users and maintain the conversation is classic >> overengineering. Seems like Seam has gone to a lot of trouble to >> provide >> just another way to persist state. > > It's not "over-engineering" to allow multiple tabs per user, each having > their own state--some applications benefit from this functionality, for > several different reasons. I bet if you gave it some thought you'd be > able to come up with several trivial examples of when and why you'd need > this functionality. > > Dave > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@struts.apache.org > For additional commands, e-mail: user-h...@struts.apache.org > > > -- View this message in context: http://www.nabble.com/Struts-2-session-problem-tp21513305p21549675.html Sent from the Struts - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
