[w3c/push-api] Rewrite introduction to clarify applicability and use cases (#218)

There were a lot of cases in the intro that hinted at use cases that push really isn't suited to.  In fact, many of the use cases were not being addressed by the API at all.  Thus, I cut things down a lot and concentrated on two:

* the webapp isn't open
* the browser is offline

I then go on to explain how messages can be sent at any time, but that push messaging is relatively inefficient (and why).

This probably needs a careful review.

Closes #179.
You can view, comment on, or merge this pull request online at:

  https://github.com/w3c/push-api/pull/218

-- Commit Summary --

  * Rewrite introduction to clarify applicability and use cases

-- File Changes --

    M index.html (78)

-- Patch Links --

https://github.com/w3c/push-api/pull/218.patch
https://github.com/w3c/push-api/pull/218.diff

-- 
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/pull/218