处理多个选项卡上的会话

问题描述:





我们的一些网站存在问题。他们的用户规模已经增长,现在这些网站现在可以在一年中的某些时间变得非常繁忙。随着越来越多的人使用它们,某些问题在网站的基本设计中得到体现,我想知道其他人如何应对这种特定情况。



这是:



我们目前在会话变量中存储与用户在网页上查看的任何内容相关的所有相关数据,这些数据存储在SQL数据库中(D B)。假设您是一名拥有5名员工的雇主。我们将在会话中存储雇主DB ID以及当前员工DB ID。我们还存储其他信息。



在打开另一个选项卡并转到同一雇主的同一页面但不同的员工时,员工的会话数据库ID现在与第一个选项卡不对应,让我们说你点击标签1上的保存按钮,你可以用标签1员工数据覆盖标签2的员工数据(姓名等 - 屏幕上的任何内容)。



希望这是基本意义。



我们对如何克服这个问题有各种各样的想法,但我很高兴听到人们对此有任何看法。 />


谢谢,



Julian

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

这是非常有趣的情况,当来自同一个浏览器的多个用户可以连接系统...

主要问题是你的数据被限制在IIS会话中,当你切换时不会切换浏览器标签......

运行ATM机时遇到同样的问题(提取信息而不是钱)在组织内的公共场所(学校)...

我们有一个解决方案......开发一个完整的子系统来处理IIS会话中的会话。我们使用GUID(动态分配)识别每个登录,并使用该GUID作为令牌,在服务器和客户端之间来回传递...

使用我们的新系统,我们正在使用ASP.NET表单登录的票证支持实现了同样的事情......
It is very interesting situation, when from the very same browser multiple users can connect the system...
The main problem is that you data is bounded to the IIS session that will not be switched when you switch browser-tab...
We had the same problem when running kind of ATM machines (to pull information and not money) in public places inside the organization (schools)...
We had a solution for that...to develop a whole sub-system to handle sessions inside IIS session. We identified every login with a GUID (dynamically assigned) and used that GUID as a token, that travels back-and-forth between the server and the client...
With our new system we are using ASP.NET form login's ticket support to achieve the very same thing...