Re: [push-api] Push API should be allowed without dependency on service worker (#84)

I think there is consensus on the public-webapps mailing list [1], at TPAC [2], and in this repo, that maintaining a dependency on service workers is appropriate. It exposes the push functionality at a low and flexible level that is composable with other APIs and allows for common patterns to evolve. Google's Chrome team has also summarized their position on the pros and cons of an imperative vs a declarative approach in [3].

I think many people also agree that there is an opportunity for optimization by combining several APIs into one (a "declarative" API) that would avoid running a service worker in certain cases. However, specifying and implementing this would be a significant amount of work, and there is not currently a lot of agreement on what the feature set would be. It has been suggested to collect use cases, and performance data and requirements, that would inform such an effort. Potential spec dependencies of such an integrated higher level API are the Push API [4], the Notifications API [5], the Telephony API [6], and the WebRTC API [7].

As such, I'd like to leave this issue open but mark it as an enhancement for a future version of the Push API, or maybe as the basis for a separate spec that depends on the Push API.

[1] https://lists.w3.org/Archives/Public/public-webapps/2014OctDec/0135.html
[2] http://www.w3.org/2014/10/27-webapps-minutes.html#item23
[3] https://docs.google.com/document/d/1kpTbKoPRaB4lXD6AMTCV2U5gTEPssQnqJj70KNb97SI/edit?usp=sharing
[4] https://w3c.github.io/push-api/
[5] https://notifications.spec.whatwg.org/
[6] http://sysapps.github.io/telephony/
[7] http://w3c.github.io/webrtc-pc/

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