Re: [push-api] Broadcast, Multi-Cast, or Topic messages via the Push API (#188)

Hi Peter, Thanks for the reply. (I lived in Richmond and contracted in London for 10 years till 2005. Miss the pubs!)

> The Push API assumes use of the Web Push Protocol, which doesn't support these features yet either. 

I guess that's what I'm asking about. Who's working on V2 of the spec? Given all the messaging services that are up and running at the moment and broadcasting 1:M being a supported feature with "mature" APIs, it can't be too hard to bring the Javascript Push API up to speed. Can it? We don't need a new wheel just one that fits our axle.

> but mandatory encryption of payloads makes it challenging to support this for anything other than tickles.

I agree. Why is it mandatory? Because we don't trust the Messaging vendor which is the same as out browser vendor? Some stuff has to be encrypted for sure but a published,broadcast,generic,context-devoid payload can surely go in the clear? But once again, how does the Java API handle it? For HTTPS can we not just rule-out CORS and use a server-hosted public key?

> your examples actually seem like cases where you would want to show a notification

You want to annoy the user with a notification every time a stock-price changes? Or do you just want to change it on the screen?

---
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/188#issuecomment-197662993