Skip to content
This repository has been archived by the owner on Sep 30, 2024. It is now read-only.

Service Worker Management #299

Open
esheehan-gsl opened this issue Apr 18, 2023 · 0 comments
Open

Service Worker Management #299

esheehan-gsl opened this issue Apr 18, 2023 · 0 comments
Labels
shaping Status for project issues that are still being discussed

Comments

@esheehan-gsl
Copy link
Contributor

Problem

The service worker speeds up the application a great deal, but there are two problems:

  1. We serve stale application assets while we update in the background, sometimes resulting in strange UI behavior until the next page load
  2. Data is cached indefinitely, so if the format changes and someone has a stale copy of the data, they never get the updated version

Solution

We should detect when the application assets have changed. If we load new CSS or JS in the background, we should notify users that they should refresh to get the latest version.

We also need to provide controls that tell users what data is available in the cache and allow them to either refresh or delete that data.

No Gos

Describe any features or behaviors that have been considered and rejected as out of scope for this project.

Rabbit Holes

Describe any solutions to problems that pose a risk to completing this project on time.

@esheehan-gsl esheehan-gsl added project shaping Status for project issues that are still being discussed labels Apr 18, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
shaping Status for project issues that are still being discussed
Projects
None yet
Development

No branches or pull requests

1 participant