Win a copy of Murach's Python Programming this week in the Jython/Python forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Session Management  RSS feed

 
Mani Ram
Ranch Hand
Posts: 1140
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have a problem somewhat similar to this
There is a login page for our application, in which the user has to enter the user id & password and clicks the Login button. This opens a new window and the user continues with the newly opened window.
Now, I switch back to the login page which is already open, and login with another user id (which opens a new window again).
This overwrites the session values of the previously logged in user also.
This happens because the session is associated with the parent window and not with the newly opened window. Is there a way to make the session to be associated with newly opened child window instead of the parent window.
Note: The application runs on WebLogic and all the pages are JSPs.
 
William Brogden
Author and all-around good cowpoke
Rancher
Posts: 13078
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Whats happening is that your browser, both parent and "child", can only have one session id cookie for the application URL. The two sessions are still there, but the application sees only the most recent.
You might be able to open a completely new browser instance to start a new session.
Bill
 
Vin Kris
Ranch Hand
Posts: 154
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Bill, I have been trying to find a way to open a new browser instance after reading your post yesterday - but I have not been able to find any solution. The closest I could get was a Bug in IE4.0 where the feature that is desired in this post was considered as a bug and fixed.
Can you please explain or direct me to some site that explains how this can be done?
I have a similar requirement and I was thinking of either preventing the user from doing so in the first place (or) allow it, but then throw an error in all such pages that were opened before the session was modified. I don't like either of the solutions.
The last and most cumbersome solution I could think of was to map evey page displayed to the session variable by using a hidden parameter in the html. That way a user can simultaneously use any number of profiles - but i'm apprehensive due to the heavy session usage in this case.
I don't want the process to be complicated for the end-user to be comprehend and at the same time I don't want to screw up the data. Opening a completely new browser instance seems the best solution.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!