I am having a problem with my web app when the user opens up multiple browser tabs to the web application. Data corruption is happening because the same session is used for all tabs, then when the user saves within a page, it overwrites some of the data in the other tab.
My first thought was to allow only one tab open per user, but thought this would be lame. So how can I provide a session container per browser tab/window so each window has it's own session?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Oh, either way, with this method, if a page is re-navigated to via a non postback, you would lose any previous data because no matter what, whether viewstate or a normal hidden field, once the page is refreshed without a postback, that unique id is lost (because the viewstate/hidden field data is lost)
Hello,
I think what you are trying to do has some drawbacks.
For example,
let's say you are using your system for some accouting purposes.
And a user opens the same window 2 times for inputting some data, if a user updates some data using one of the windows; and at a second time uses the second window to change the same data, you will face with data inconsistencies even if you are using different sessions.
Maybe you are searching the solution in the wrong direction.
You are absolutely right.
I also found this great article to help put me in the right direction:
http://www.odetocode.com/A
Thanks all for the advise.
Business Accounts
Answer for Membership
by: robkolskyPosted on 2009-09-14 at 06:24:15ID: 25325083
Sesions are shared across multiple instances of the same browser (i.e. tabs). If this is all within one page, you would be much better served by storing data in ViewState which is completely isolated to the specific instance of that page, and will persist as long as that copy of the page is active. That way data on multiple browser tabs will never interact with each other.
However, if you absolutely need session variables...
How you are going to handle this will depend on how you have structured your forms. Basically, you want to create a class that stores all the data you want to put into various session variables. You can then store a class instance in a session variable. First you need to create a viewstate field (or hidden field) that stores a uniqueid. You would only generate this id if the page is not posting back, otherwise you can pull the id from the viewstate field. You can then use that ID as the name of your session variable to be able to retrieve the variable.