Re: [w3c/push-api] Allow Subscription via TOPIC headers (#189)

I am at a complete loss to explain why someone would deliberately seek to ham-string the Web Push API and then go on to shoot itself in the foot after putting out enough sand-bags to ensure that it could never compete with native App API implementations :-(

> As you can read in the abstract of the Push API, this API is being 
> designed specifically for use with the Web Push Protocol,

Did you miss this bit: -
[[[[[[
Alternative protocols could be used in place of this protocol, but this specification assumes the use of this protocol; alternative protocols are expected to provide compatible semantics.
]]]]]]

How the Application Server communicates with the push service is of little concern to you and thankfully outside your sphere of influence. When is comes to the UA it is the same feature-detection, degrade-gracefully, iterative and incremental development that we all know and love. If a particular UA does not support topic-based subscription then so be it. Nothing in that feature limitation mandates a lowest-common-denominator approach for the specification.

> not to provide the union of features provided 
> by the many push services out there.

“Broadcasting” is an intrinsic and integral part of any Push Messaging architecture! Even if it’s not there in V1.0, surely the hooks should be left in place for future improvements? With the MBONE team looking to finally release something, the performance improvements could be amazing!

- BROADCASTING
- PRIORITY
- TTL
- COLLAPSE_KEY
- TOPIC Subscription

They are just some of the desirable features on the futures list. The beauty is that POC implementations are already out there; the work’s been done. 

> I'm afraid this feature request is a WontFix from the Push API's point of view.

Is there nobody here at Martintown Guyana willing to suggest we’re going the wrong way? Mozilla abandoned Simple Push and Microsoft is coming onboard with the Web Push API. Their users are getting Fed up with design 180s. Please make the design extensible!

Am I not asking for goodness?

“Thank-you for not discussing the outside world.”
                                   – W3C and IETF mgmnt.

![image](https://cloud.githubusercontent.com/assets/8264706/14415488/46adec06-ffd2-11e5-88e6-35d92c879d22.png)


---
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/189#issuecomment-208132066