HttpServletResponse.encodeURL http://java.sun.com/products/servlet/2.2/javadoc/javax/servlet/http/HttpServletResponse.html#encodeURL(java.lang.String)
Martin ______________________________________________ Disclaimer and confidentiality note Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission. > From: andrh...@hotmail.com > To: user@struts.apache.org > Subject: RE: Struts 2 session problem > Date: Mon, 19 Jan 2009 17:07:13 -0600 > > > I agree with ya. I have been doing something very similar with hidden fields > in my app for some time. The server knows if a new browser instance is > requested by checking the hidden field. If its empty it then creates a new > key and sets the hidden field. Basically partitions the session based on > keys. At the end of the day a servlet container creates a single session for > a single workstation. > > > > > Date: Mon, 19 Jan 2009 12:39:30 -0800 > > From: glindh...@yahoo.com > > To: user@struts.apache.org > > Subject: Re: Struts 2 session problem > > > > > > Yes, SEAM does: > > > > http://www.seamframework.org/Documentation/DoesSeamSupportMultipleBrowserWindowsOrTabs > > > > I haven't dug into exactly how they do it but I would not be surprised if > > they pass around a hidden conversation token with every request. Then any > > state information that gets stored in the session would include the > > conversation id. > > > > Passing around a conversation token is something a developer could do > > manually, but it's also a feature that could be built into the framework to > > make it easy for all to use. > > > > > > Jim Kiley wrote: > > > > > > Are there frameworks that handle this situation differently? It's a > > > browser-side issue, so it isn't clear to me how a server-side framework > > > could solve it. > > > jk > > > > > > On Mon, Jan 19, 2009 at 3:02 PM, Greg Lindholm <glindh...@yahoo.com> > > > wrote: > > > > > >> > > >> Oh I fully understand this is a issue with how browsers deal with > > >> sessions. > > >> However these are the browsers our apps have to work with so as a > > >> developer > > >> I have to make the apps work with them and I expect any decent app > > >> framework > > >> to have good solutions to all the common use cases. And I consider having > > >> multiple windows/tabs open to the same app a very common use case. > > >> > > >> If some other framework (like SEAM) is handling this issue better then > > >> let > > >> see if we can implement the same solution in Struts 2. > > >> > > >> Correction: In my last post I meant to say "Conversation token" not > > >> "Session token". > > >> > > >> > > >> Rubbinio wrote: > > >> > > > >> > 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 > > >> > > > >> > > > >> > > > >> > > >> -- > > >> View this message in context: > > >> http://www.nabble.com/Struts-2-session-problem-tp21513305p21550453.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 > > >> > > >> > > > > > > > > > -- > > > Jim Kiley > > > Technical Consultant | Summa > > > [p] 412.258.3346 [m] 412.445.1729 > > > http://www.summa-tech.com > > > > > > > > > > -- > > View this message in context: > > http://www.nabble.com/Struts-2-session-problem-tp21513305p21551088.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 > > > > _________________________________________________________________ > Windows Live™: Keep your life in sync. > http://windowslive.com/howitworks?ocid=TXT_TAGLM_WL_t1_allup_howitworks_012009 _________________________________________________________________ Windows Live™: Keep your life in sync. http://windowslive.com/explore?ocid=TXT_TAGLM_WL_t1_allup_explore_012009
