Re: [push-api] events should be part of PushSubscription (#104)

The spec depends on Service Workers, e.g. see the first paragraph of the abstract:

> A push service allows a webapp server to send messages to a webapp, regardless of whether the webapp is currently active on the user agent. The push message will be delivered to a Service Worker[...]

This enables the following part of the use case section [1]:

> the webapp is not currently active in a browser window: this relates to use cases in which the user may close the webapp, but still benefits from the webapp being able to be restarted when a push message is received

The `PushManager` is only exposed on `ServiceWorkerRegistration` for this reason:
https://w3c.github.io/push-api/#extensions-to-the-serviceworkerregistration-interface

Without Service Workers the user agent would have to spin up a web page, with most likely far higher CPU, memory, and network requirements.

https://w3c.github.io/push-api/#introduction

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/push-api/issues/104#issuecomment-69567858