{"action":"closed","issue":{"url":"https://api.github.com/repos/greatfire/redirect-when-blocked/issues/5","labels_url":"https://api.github.com/repos/greatfire/redirect-when-blocked/issues/5/labels{/name}","comments_url":"https://api.github.com/repos/greatfire/redirect-when-blocked/issues/5/comments","events_url":"https://api.github.com/repos/greatfire/redirect-when-blocked/issues/5/events","html_url":"https://github.com/greatfire/redirect-when-blocked/issues/5","id":51802987,"number":5,"title":"ServiceWorker?","user":{"login":"requiredfield","id":6235698,"avatar_url":"https://avatars.githubusercontent.com/u/6235698?v=3","gravatar_id":"","url":"https://api.github.com/users/requiredfield","html_url":"https://github.com/requiredfield","followers_url":"https://api.github.com/users/requiredfield/followers","following_url":"https://api.github.com/users/requiredfield/following{/other_user}","gists_url":"https://api.github.com/users/requiredfield/gists{/gist_id}","starred_url":"https://api.github.com/users/requiredfield/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/requiredfield/subscriptions","organizations_url":"https://api.github.com/users/requiredfield/orgs","repos_url":"https://api.github.com/users/requiredfield/repos","events_url":"https://api.github.com/users/requiredfield/events{/privacy}","received_events_url":"https://api.github.com/users/requiredfield/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2014-12-12T12:53:32Z","updated_at":"2015-06-25T03:02:45Z","closed_at":"2015-06-25T03:02:45Z","body":"Does ServiceWorker buy us anything over AppCache?\r\n\r\nJust came across http://jakearchibald.com/2014/offline-cookbook/ which says:\r\n\r\n> When AppCache arrived on the scene it gave us a couple of patterns to make content work offline. If those were the patterns you needed, congratulations, you won the AppCache lottery (the jackpot remains unclaimed), but the rest of us were left huddled in a corner [rocking back & forth](http://alistapart.com/article/application-cache-is-a-douchebag).\r\n>\r\n> With ServiceWorker ([intro](http://www.html5rocks.com/en/tutorials/service-worker/introduction/)) we gave up trying to solve offline, and gave developers the moving parts to go solve it themselves. It gives you control over caching and how requests are handled. That means you get to create your own patterns. Let's take a look at a few possible patterns in isolation, but in practice you'll likely use many of them in tandem depending on URL & context.\r\n>\r\n> All code examples work today in Chrome 40 beta with the [cache polyfill](https://github.com/coonsta/cache-polyfill), unless otherwise noted. This stuff will land into the stable version January/February 2015 barring any emergencies, so it won't be long until millions of real users can benefit from this stuff.\r\n>\r\n> For a working demo of some of these patterns, see [Trained-to-thrill](https://jakearchibald.github.io/trained-to-thrill/), and [this video](https://www.youtube.com/watch?v=px-J9Ghvcx4) showing the performance impact.\r\n>\r\n> (cookbook contents follow)\r\n\r\nIf so, I guess we can keep an eye on https://developer.mozilla.org/en-US/docs/Web/API/ServiceWorker_API#Browser_support for support in other browsers."}}