Closed
Bug 1147061
Opened 10 years ago
Closed 7 years ago
Expose fetch Response.body and Request.body as streams
Categories
(Core :: DOM: Core & HTML, defect, P2)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
DUPLICATE
of bug 1128959
Performance Impact | none |
Tracking | Status | |
---|---|---|
platform-rel | --- | + |
People
(Reporter: bkelly, Assigned: valentin)
References
(Blocks 1 open bug)
Details
(Whiteboard: [platform-rel-Facebook])
We should investigate and consider implementing Request.body and Response.body attributes as streams. Proposal is here:
https://github.com/yutakahirano/fetch-with-streams
Blink intends to ship an implementation:
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/35_QSL1ABTY
Reporter | ||
Updated•8 years ago
|
Blocks: ServiceWorkers-streams
Comment 1•8 years ago
|
||
Tracking under 'platform-rel-Facebook'. This issue is blocking Facebook from rolling out service worker to users and providing more feedback on Firefox's implementation.
Whiteboard: platform-rel-Facebook
Updated•8 years ago
|
platform-rel: --- → +
Whiteboard: platform-rel-Facebook → [platform-rel-Facebook]
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → valentin.gosu
Whiteboard: [platform-rel-Facebook] → [platform-rel-Facebook][necko-active]
Updated•8 years ago
|
Whiteboard: [platform-rel-Facebook][necko-active] → [platform-rel-Facebook]
Comment 2•7 years ago
|
||
I've been told once facebook rolls this out Chrome will receive a considerable startup perf boost relative to firefox if we don't support this. We should see if we need this to be competitive.
Flags: needinfo?(dchinniah)
Whiteboard: [platform-rel-Facebook] → [platform-rel-Facebook][qf]
Comment 3•7 years ago
|
||
adding dev-doc-needed, just in case we need to update docs as a result.
Keywords: dev-doc-needed
(In reply to Bas Schouten (:bas.schouten) from comment #2)
> I've been told once facebook rolls this out Chrome will receive a
> considerable startup perf boost relative to firefox if we don't support
> this. We should see if we need this to be competitive.
Adding :overholt for his direction...
Flags: needinfo?(dchinniah) → needinfo?(overholt)
Comment 5•7 years ago
|
||
Thanks for bringing this up, Bas. We're aware of some of the work Facebook has been doing here and have requested some more information (they have already been great about sharing their results). If that comes back showing that this is super super important, we'll see if we can shuffle this bug's priority. Barring that, this is still on our "next most important thing" list.
Flags: needinfo?(overholt)
Priority: -- → P2
Updated•7 years ago
|
Whiteboard: [platform-rel-Facebook][qf] → [platform-rel-Facebook][qf-]
Comment 6•7 years ago
|
||
I'm implementing this feature in bug 1128959.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Comment 7•7 years ago
|
||
The important thing is the design of this api. It might permits not only to use a byte reader but also a way for transforming a stream in another stream. For example you receive a particular text stream and it convert it another stream after a manupulation.
In addition it is necessary to create a custom reader/writer also in javascript not only in native code. I could create a algorithm generating a stream(for example a sound,...). This api in future might replace a lot of not mature api for reading/writing video/audio streams.
Updated•7 years ago
|
Keywords: dev-doc-needed
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
Updated•3 years ago
|
Performance Impact: --- → -
Whiteboard: [platform-rel-Facebook][qf-] → [platform-rel-Facebook]
You need to log in
before you can comment on or make changes to this bug.
Description
•