Timeline for Delete user data when they sign out?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 1, 2017 at 6:27 | comment | added | BiGGZ | at the end of the day sir, your sugesstion of making the application read-only when there is no internet connection as opposed to tracking transactions and syncing later really is the answer to my dilemma, thanks a lot | |
| Jan 1, 2017 at 1:03 | comment | added | BiGGZ |
I think that only allowing one connection to connect to the server at a time, and putting all other devices into an offline mode should be satisfactory . Thats pretty much my intention hey, because my use case makes extensive use of push notifications, so because of that, the server only expects to have one token(used to communicate downstream) per user at a time, so if the server detects the token received and the token stored are not the same, thats when the device represented by the stored token is forcefully signed out. Not sure if that makes sense?
|
|
| Jan 1, 2017 at 0:07 | comment | added | Blair | When you say that they are forcefully signed out. Are you trying to limit a user's ability to access the local dataset if they have signed into another device? Personally, I think this is overkill. I think that only allowing one connection to connect to the server at a time, and putting all other devices into an offline mode should be satisfactory. This also solves your issue of trying to sign out an already offline device, because as far as the user is concerned (and the server) there is no difference. Then you can require another sign in on reconnect. | |
| Dec 30, 2016 at 21:55 | comment | added | BiGGZ | But this too leaves a lot to be desired because if there is no internet connection on the device being forcefully signed out, there could still be anomalies in that the syncing mechanism will kick in a lot later(or not at all) and the currently signed in device will never know. | |
| Dec 30, 2016 at 21:54 | comment | added | BiGGZ | This right here is the best/simplest/most straight-forward route. Thanks a lot. My current implementation allows full read/write and tracks two things: 1. The failed transactions and 2. The internet connection status. When a connection is re-established, the data is synced. In addition, if the user signs in on another device, they will be forcfully signed out of the other device(if there is no connection, the sign-out signal is persisted and re-sent when a connection has been established, thus performing a sync opp if necessary) | |
| Dec 30, 2016 at 21:52 | review | Late answers | |||
| Dec 31, 2016 at 11:29 | |||||
| Dec 30, 2016 at 21:47 | comment | added | BiGGZ |
I would strongly push to put the application into a read only offline mode. So if X goes offline, it can read the local data store (or cache) but it cannot make changes or delete records until a connection is established.
|
|
| Dec 30, 2016 at 21:46 | vote | accept | BiGGZ | ||
| Dec 30, 2016 at 21:33 | history | answered | Blair | CC BY-SA 3.0 |