- From: Marco Colli <notifications@github.com>
- Date: Mon, 03 Sep 2018 04:38:38 -0700
- To: w3c/push-api <push-api@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 3 September 2018 11:38:59 UTC
@pete10 I agree with you that currently there is no way to properly manage the case of "session expiration" (maybe adding a new event `sessionexpired` to the service worker can solve that). Currently the only workaround would be to **add an expiration date to the user ID in your database**: e.g. instead of having *[endpoint, user_id]* you can use *[endpoint, user_id, uid_valid_through]*. However the expiration date would be always different from the session expiration. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/push-api/issues/297#issuecomment-418089329
Received on Monday, 3 September 2018 11:38:59 UTC