mquan / turbo-issues

bug tracking for turbo
0 stars 0 forks source link

Notifications aren't reloaded when logged back from lockscreen #121

Closed mquan closed 11 years ago

mquan commented 11 years ago

Every time a user locks screen, all notifications must be deleted and reloaded upon reloggin

mquan commented 11 years ago
  1. Upon locking screen, remove all notifications from orders and conversations. But do not delete the notifications b/c when the same user log back in, these notifications were marked as deleted are now loaded and ember-data will cause error.
  2. When unlock successfully (relogin), all conversations and notifications will be reloaded from the server specific to this user. On client side, 'notifications loaded' and 'conversations loaded' events are triggered and just follow its natural progression as if the page was just refreshed.
  3. To improve on performance, branch, orders, and archives are not sent back. Moreover, this will prevent the problem of overloading orders that are changed locally but have not been committed.

The only downside to this solution is if a store has many users using the same machine, over time all of their notifications and conversation will be loaded locally, this may cause slowness in client. It has to be a lot of user, b/c notifications will be removed as orders are archived.