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

Great minds (not just Google): -

https://blogs.windows.com/buildingapps/2013/09/16/delivering-push-notifications-to-millions-of-devices-with-windows-azure-notification-hubs/

_Efficient tag-based multicast and pub/sub routing. Devices can specify one or more tags when registering with a Notification Hub. This indicates a user’s interest in notifications for a set of topics (favorite sport/teams, geo location, stock symbol, logical user ID, and so on). These tags don’t need to be pre-provisioned or disposed, and provide a very easy way for apps to send targeted notifications to millions of devices with a single API call, without you having to implement your own per-device notification routing infrastructure._

https://aws.amazon.com/sns/

_Engage audiences directly or all-at-once 
Use direct-addressing to send messages to individual devices or broadcast to multiple destinations at-once._

Who'd 've thunk it?

Those who can, do! Those that can't, teach! Those who couldn't find their arse in the dark with two hands and a torch, write standards!

---
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-208720449