保留用户登录Cookie密钥的数据库设计
[英]Database design for keeping-user-logged-in cookie key
问题描述
So I am using this approach to keep users logged in, and I am wondering about a few things before I build my data tables. 
因此，我正在使用这种方法来保持用户登录状态，并且在构建数据表之前我想知道一些事情。
If a user is able to log in even when they are already logged in (this shouldn't happen but it might), and thus two or more cookies are generated and stored on the users computer, how does my PHP script know which is the correct cookie to validate? 如果用户即使已经登录也能够登录（这种情况不应该发生，但是可能会发生），因此在用户计算机上生成并存储了两个或多个cookie，我的PHP脚本如何知道哪个是正确的cookie以进行验证？ Do cookies overwrite each other? Cookie是否会相互覆盖？
Of course, if I keep a key for every key they generate, it wouldn't matter much which cookie they provided, however this leads me to my next question: 当然，如果我为它们生成的每个密钥都保留一个密钥，那么它们提供的cookie无关紧要，但这使我想到了下一个问题：
What database design should I use to get rid of old cookies? 我应该使用哪种数据库设计来摆脱旧的Cookie？ I can't imagine storing a key for every instance of them logging in. In my short time as a web developer I have not made a database that keeps only the newest instance of an event, and deletes the old one. 我无法想象为他们登录的每个实例存储一个密钥。在作为Web开发人员的短时间内，我还没有建立一个仅保留事件的最新实例并删除旧实例的数据库。
Sincere thanks for any help, it is greatly appreciated. 真诚的感谢您的帮助，我们将不胜感激。
0 个解决方案
声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.