- From: Matthew Gaunt <notifications@github.com>
- Date: Wed, 07 Jan 2015 09:37:27 -0800
- To: w3c/push-api <push-api@noreply.github.com>
Received on Wednesday, 7 January 2015 17:38:18 UTC
Hence the API will be blocked on push services implementing changes - big negative since it blocks the API from being useful. The alternative is to supply info on the push services via some API, including the notion of type (i.e. open standard or proprietary). Regardless - identification of the service will be possible via the endpoint url, but that is post permission UI, which is a poor user experience. If UA's will be able to use proprietary push services (like Chrome is today with GCM) - or it's an option for a UA, then an API to examine the endpoints pre-permission UI needs to be included. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/push-api/issues/95#issuecomment-69059147
Received on Wednesday, 7 January 2015 17:38:18 UTC