What are the benefits of logging on to the same account with two devices and logging out of another device account?
Thank you!
Reply content:
What are the benefits of logging on to the same account with two devices and logging out of another device account?
Thank you!
There is no special benefit, depending on the demand. As for the Pirates upstairs there is a certain truth, but is not the most critical (for example, can also be based on the IP location to determine the theft number).
Exclusive checks of account logins are resource-intensive, with no difference in core principles and "who is online". This is not a burden for chat software, but it usually doesn't make any sense for other applications.
You should ask yourself a question before using this feature: If you really have two clients logged in to the same account at the same time, what are the implications for business logic? Does this impact cause the business logic to be abnormal?
In fact, multi-client login to the same account is very common, especially for the site, such as users like to browse the site in a browser, and he received a message from the site, and the URL in the mailbox will be opened in the default browser system settings. It would have been normal, but it would have been steeds if I had found myself kicked out of the browser on a.
Chat software does not like this matter, because this has the impact, because the data to the multi-side forwarding to increase the pressure, originally good point-to-point chat into 3-party calls, more uncomfortable.
Feel you ask, never find your answer
Proposed to change the problem, the business scenario is described briefly, if it is a third-party product can also be explicitly
For example, why not support two devices to log on to the same account? Sort of, humble opinion, for reference only.
To prevent stolen numbers from knowing
There is a very real scene, the same content, the user operates on two sides.
Feel not to say point on, multiple end at the same time online, for the client, no difference, for the server side, can be a very headache, such as the following situation:
1, data synchronization, ABC three has landed your app,a data is January, b data is February, C data is March, the latest data is April, how to synchronize to the ABC three end (of course you can choose the full volume of synchronization, but not too low? ), as well as the updated state save, etc.
2, three end at the same time to modify a piece of data, who is the right, do not think with time stamp can solve? High concurrency, OK?
3, three side add data at the same time?
Wait a minute
In this way, it is not easy to find a single device login processing is not much easier.