Hi,
We have an issue with a few of our sites. They have grown in user size of the years and the sites can now get quite busy at certain times of the year/month. With more people using them, certain issues are coming to light in the esential design of the sites, and I was wondering how other people would cope with this specific situation.
Here it is:
We currently store all pertinent data relating to anything that the user is looking at on the web pages in session variables, which are stored in a SQL Database (DB). Let's say you are an employer with 5 employees. We will store the employer DB ID in the session along with the current employee DB ID. We also store other information.
On opening another tab and going to the same page for the same employer but different employee, the session DB ID for the employee will now not correspond with the first tab, and let's say you click the save button on tab 1, you could be overwriting tab 2's employee data (name etc. - whatever is on screen) with tab 1 employee data.
Hope that makes basic sense.
We have various ideas on how to overcome this, but I would be happy to hear any views people have on this.
Thanks,
Julian