blocks|key|941051|text|当然，您可以使用客户端轮询器脚本来实现这一点。在JavaScript中，你可以生成一个窗口ID，它可以是任何东西，只要它保证是唯一的。让JS让Ajax调用者访问服务器上的一个端点，该端点只比较ID和会话。在任何时候，如果你有两个不同的"windowID“值，你知道它们必须为同一会话打开窗口。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|941052|您可以在服务器端将其存储为会话中的数组，甚至可以将其完全存储在客户端的cookie中。如果您选择这样做，您的客户端轮询器将只查看cookie值，如果它包含两个不同的值，则说明有问题。然而，Cookie不太理想，因为它们增加了请求/响应周期的权重，并且您必须设置一种机制，以便在用户卸载页面时清除当前页面的值。|941053|对于服务器端实现，您只需要将当前的windowID与链接或post一起发送，这样服务器就可以从会话中清除windowID。然而，所有这些都不能防止用户同时打开Firefox会话和Chrome会话。|941054|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Sure, you can achieve this with a client-side poller script. In JavaScript, you can generate a window ID that can be anything as long as its guaranteed to be unique. Have the JS make Ajax callers to an endpoint on the server that does nothing but compare IDs and session. At any point if you have two different "windowID" values, you know they have to have to windows open for the same session. 

You could store this on the server side as an array in the session or you could even store it entirely on the client side in a cookie. If you chose to do that, your client side poller would just look at the cookie value and if it contains two different values, something is amiss. Cookies are a little less ideal though because they add weight to the request/response cycle and you'd have to setup an mechanism to clear the value of the current page when the user unloads the page. 

For the server-side implementation, you would just need to send the current windowID along with link or post so that the server can clear the windowID from the session. None of this would protect against the user having a Firefox session and a Chrome session open at once though.

blocks|key|941067|text|您可以在第一步首次启动时将会话标记为已启动。确保服务器端遵循正确的步骤(即，在步骤1完成后，他们不会返回到步骤1，除非他们特别单击一个链接来执行此操作)。基本上，跟踪他们在服务器上的当前步骤，并根据需要进行更新。如果用户做了一些意想不到的事情，您可以让他们选择从头开始。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|941068|我想知道表单上带有时间戳的隐藏字段是否会有所帮助。不过也有些类似的想法。|941069|注意:这个过程可能会破坏浏览器后退按钮的本质。我恨我自己让它在我的一个项目中发生。|941070|对于跨浏览器支持，您需要将其与用户帐户或持久存在的内容相关联。|941071|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

You could mark a session as started when step 1 is first started. Make sure server-side that they follow the right steps (i.e. they don't return to step 1 after step 1 has been completed unless they specifically click a link to do so.) Basically, track their current step on the server and update it as needed. In the event the user does something unexpected, you could give them the option to start over.

I'm wondering if hidden fields with timestamps on your forms might help. Kinda the same idea though.

Caveat: this process might break the essence of your browser's back button. I hate myself for letting that happen in one of my projects.

For cross-browser support, you'd need to have it associated with a user account or something that persists.

blocks|key|725051|text|1.相同的问题(和解决方案)：https://sites.google.com/site/sarittechworld/track-client-windows|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|725052|2.您可以通过POST或GET方式发送信息|725053|entityMap|0|LINK|mutability|MUTABLE|url|https://sites.google.com/site/sarittechworld/track-client-windows^0|F|1T|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

1.The same problem (and solution) : <a href="https://sites.google.com/site/sarittechworld/track-client-windows" rel="nofollow noreferrer">https://sites.google.com/site/sarittechworld/track-client-windows</a>

2.You can send information by POST or GET

blocks|key|941137|text|正如本杰明所指出的，您可以通过提出每个窗口的ID来实现这一点，然后在每次请求时将其报告给服务器。如果您想启用多窗口用例，我认为这是最合理的方法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|941138|我不认为您需要通过ajax轮询服务器才能做到这一点。只要对服务器的每个请求都包含窗口ID，您就可以消除服务器端与请求相关联的会话的歧义。这意味着您的服务器端代码必须更改，以便将窗口ID作为会话的一部分。|941139|然而，这种方法有严重的缺点。例如，如果用户同时关闭Tab+A和Tab+B，然后打开一个新的Tab+C...会发生什么？他们应该重新连接哪组数据？|941140|如果您需要防止将多个选项卡混合在一起，那么将用户限制在单个选项卡中的方法听起来非常合理。|941141|你可以通过本地存储来做到这一点。如果您在客户机上生成一个随机ID，并通过像window.localStorage.setItem('window_id',+<my_random_id_here>);这样的调用将其推送到本地存储中，那么您可以在页面加载时检查此值。如果该值在页面加载时存在，那么您已经非常清楚地表明至少有一个其他窗口是打开的。您必须确保在页面卸载时删除此值，否则死会话可能会触发误报。|offset|length|style|CODE|941142|entityMap^0|0|0|0|0|11|1Q|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|S|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@$J|U|K|V|L|M]]|9|@]|A|$]]|$1|N|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|O|$]]

As Benjamin pointed out, you can do this by coming up with a per-window ID which you then report to the server with each request. If you want to enable the multiple window use case, I think this is the most reasonable approach. 

I don't think you need to poll the server via ajax to do this though. As long as every request to the server includes the window ID, you can disambiguate what session on the server side to associate the request with. That will mean that your server-side code has to change to include the window ID as part of the session.

However, that approach has serious drawbacks. For instance, if the user closes both Tab A and Tab B, and then opens up a new Tab C... what happens? Which set of data should they reconnect with?

The approach of restricting the user to a single tab sounds pretty reasonable if you need to prevent the intermingling of multiple tabs worth of state. 

You can do this via Local Storage, btw. If you generate a random ID on the client and push it into Local Storage via a call like <code>window.localStorage.setItem('window_id', &lt;my_random_id_here&gt;);</code> then you can check for this value on page load. If the value exists when the page loads, you've got a pretty clear indicator that at least one other window is open. You'll have to make sure to remove this value on page unload, otherwise dead sessions might trigger false positives.

I've done a booking application done using CakePHP which involves a few steps before the checkout page. In between these steps I store the information in the session. 

How it works is that Step 1 requires them to fill in their information. When going to Step 2, the information in Step 1 will be saved into the session object. As they proceed in the other steps, the process repeats. At the end when they checkout, all the data is then saved to the database.

Everything works great if the user opens one instance of the application in the browser. But once they have another page or another tab opened for the same application in the same browser, problem happens.

Let's say they have two instance of the application open in Tab A and Tab B. In Tab A they entered the details in Step 1 and proceed to Step 2. Then the user does the same thing in Tab B.

At the last step when the user does a checkout, information in Tab A is the same as in Tab B.

Right now, I can only think the best way is to prevent the user from opening the same application in two browser instance. 

Is there a way to detect and prompt the user to complete the booking form in Tab A first when they try to open another instance in Tab B?

How to detect if user open two tabs for same session?

数据库

服务器

我已经用CakePHP做了一个预订应用程序，它涉及到结账页面之前的几个步骤。在这些步骤之间，我将信息存储在会话中。它的工作原理是，步骤1要求他们填写他们的信息。当转到步骤2时，步骤1中的信息将保存到session对象中。当它们在其他步骤中进行时，该过程重复。最后，当他们结帐时，所有数据都会保存到数据库中。如果用户在浏览...

问如何检测用户是否为同一会话打开了两个选项卡？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何检测用户是否为同一会话打开了两个选项卡？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何检测用户是否为同一会话打开了两个选项卡？
EN