Skip to content
This repository has been archived by the owner on Oct 2, 2020. It is now read-only.

Service Worker API - Blurb #44

Closed
ashleymichal opened this issue May 3, 2019 · 1 comment
Closed

Service Worker API - Blurb #44

ashleymichal opened this issue May 3, 2019 · 1 comment
Labels
articles Short articles on best practices

Comments

@ashleymichal
Copy link
Contributor

ashleymichal commented May 3, 2019

In addition to the pages about FetchEvent and CacheAPI, include a short blurb about our implementation of the Service Worker API; previous versions of our documentation simply said we implemented "as much as makes sense", which is only intuitive if you are already familiar with the product. This piece should indicate something about the lifecycle (or lack thereof) of our Service Worker implementation -- scripts are pushed to the edge, rather than downloaded like they are in the browser, so installation and activation steps are unnecessary; additionally, all implementation tied to the attempt to sync up the versions of all instances of service workers, as is done in the browser, is impractical for our 6000+ machine network, and therefore we don't attempt, meaning that more than one version of your script may be active at a time across our network.

@ashleymichal
Copy link
Contributor Author

ashleymichal commented May 24, 2019

this will just serve to confuse users. we will instead focus on a "lifetime of a request" #160 article for post-launch.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
articles Short articles on best practices
Projects
None yet
Development

No branches or pull requests

2 participants