How long can the service worker stay awake during an active fetch
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 3.6k
- Forks
- 324
- Avg merge
- 14d 22h
- Merged PRs (30d)
- 1
Description
This issue was WONTFIX'd https://bugs.chromium.org/p/chromium/issues/detail?id=753646 because "Chrome stops the service worker after 5+ minutes timeout even if it is streaming."
This means it's impossible to use service worker to serve a stream of a 2hr movie.
I feels like we should enable this somehow. Eg fetchEvent.waitUntil should be able to keep the service worker alive for as long as the fetch is in-progress.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing Chromium issue 753646 and the service worker lifetime behavior described here. Determine whether fetchEvent.waitUntil should keep a service worker alive for the duration of an in-progress streaming fetch, and define the specification resolution for that behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100