Open
Bug 1283191
(ServiceWorkers-streams)
Opened 8 years ago
Updated 2 years ago
[meta] Service worker streaming
Categories
(Core :: DOM: Service Workers, enhancement, P3)
Core
DOM: Service Workers
Tracking
()
NEW
People
(Reporter: bkelly, Unassigned)
References
(Depends on 6 open bugs)
Details
(Keywords: meta)
One of the main use cases for streams right now is in service workers. Even with streams API support, though, we have a number of issues to solve to make streams work well in service workers. There are a number of places we stop to accumulate data or otherwise don't handle streams quite right. This meta bug is to track fixing these issues.
Comment 1•8 years ago
|
||
Stream support in ServiceWorkers is becoming quite important to us at Wikimedia. We recently prototyped streaming HTML composition in a ServiceWorker (see https://github.com/wikimedia/web-stream-util and https://github.com/wikimedia/node-serviceworker). First performance results in Chrome look really attractive, with reductions in time-to-useful-page especially on slow connections. To provide similar speed-ups & offline support in Firefox, we will need - a body stream returned from fetch, - stream support in caches, - the ability to construct & return a ReadableStream from a ServiceWorker.
Reporter | ||
Comment 2•8 years ago
|
||
I agree we need someone working on this, but unfortunately I don't have the bandwidth right now.
Assignee: bkelly → nobody
Status: ASSIGNED → NEW
Reporter | ||
Updated•8 years ago
|
Blocks: ServiceWorkers
Reporter | ||
Updated•7 years ago
|
Depends on: streams-enable
Comment 4•5 years ago
|
||
I assume, we still want to complete this. :asuth, can you check if the dependencies are up to date?
Type: defect → enhancement
Flags: needinfo?(bugmail)
Comment 5•5 years ago
|
||
Deps are up-to-date although we will probably need to file some additional bugs when we really dig into the architecture of this, but that's a multi-day affair. (Maybe this should happen as part of the architectural review?)
Flags: needinfo?(bugmail)
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•