{"action":"created","issue":{"url":"https://api.github.com/repos/w3c/push-api/issues/74","labels_url":"https://api.github.com/repos/w3c/push-api/issues/74/labels{/name}","comments_url":"https://api.github.com/repos/w3c/push-api/issues/74/comments","events_url":"https://api.github.com/repos/w3c/push-api/issues/74/events","html_url":"https://github.com/w3c/push-api/issues/74","id":45370908,"number":74,"title":"pushregistrationlost use case","user":{"login":"mvano","id":5739872,"avatar_url":"https://avatars.githubusercontent.com/u/5739872?v=3","gravatar_id":"","url":"https://api.github.com/users/mvano","html_url":"https://github.com/mvano","followers_url":"https://api.github.com/users/mvano/followers","following_url":"https://api.github.com/users/mvano/following{/other_user}","gists_url":"https://api.github.com/users/mvano/gists{/gist_id}","starred_url":"https://api.github.com/users/mvano/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mvano/subscriptions","organizations_url":"https://api.github.com/users/mvano/orgs","repos_url":"https://api.github.com/users/mvano/repos","events_url":"https://api.github.com/users/mvano/events{/privacy}","received_events_url":"https://api.github.com/users/mvano/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":9,"created_at":"2014-10-09T14:13:30Z","updated_at":"2015-01-12T16:10:44Z","closed_at":null,"body":"@efullea @miguelgarciaarribas @martinthomson\r\n\r\nHow does the `pushregistrationlost` event use case work? The spec currently says to fire it `Upon any event that makes a push registration no longer valid, e.g. push server database failure`. Presumably the client would then reregister to recover from this failure.\r\n\r\nIf the push server suffers a database failure and loses registration data, how can it notify the (previously) registered client?\r\n\r\nDo we have any use cases that make more sense? Or can we just drop the `pushregistrationlost` event from the spec?"},"comment":{"url":"https://api.github.com/repos/w3c/push-api/issues/comments/69594163","html_url":"https://github.com/w3c/push-api/issues/74#issuecomment-69594163","issue_url":"https://api.github.com/repos/w3c/push-api/issues/74","id":69594163,"user":{"login":"gauntface","id":139760,"avatar_url":"https://avatars.githubusercontent.com/u/139760?v=3","gravatar_id":"","url":"https://api.github.com/users/gauntface","html_url":"https://github.com/gauntface","followers_url":"https://api.github.com/users/gauntface/followers","following_url":"https://api.github.com/users/gauntface/following{/other_user}","gists_url":"https://api.github.com/users/gauntface/gists{/gist_id}","starred_url":"https://api.github.com/users/gauntface/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gauntface/subscriptions","organizations_url":"https://api.github.com/users/gauntface/orgs","repos_url":"https://api.github.com/users/gauntface/repos","events_url":"https://api.github.com/users/gauntface/events{/privacy}","received_events_url":"https://api.github.com/users/gauntface/received_events","type":"User","site_admin":false},"created_at":"2015-01-12T16:10:44Z","updated_at":"2015-01-12T16:10:44Z","body":"Thanks @mvano was looking at w3 spec and then obviously missing that bug. Tracking that."}}