The streams APIs provide ubiquitous, interoperable primitives for creating, composing, and consuming streams of data. A natural thing to do with a stream is to pass it to a web worker. This provides a fluent primitive for offloading work to another thread. Transferable streams add this capability by allowing ReadableStream, WritableStream, and TransformStream objects to be passed as arguments to postMessage().

Motivation

Offloading work onto a worker is important for a smooth user experience, but the ergonomics can be awkward. Transferable streams solve this problem for streams. Once the stream itself has been transferred, the data is transparently cloned in the background.

Demo

• https://github.com/whatwg/streams/blob/master/transferable-streams-explainer.md

Documentation

• https://docs.google.com/document/d/1_KuZzg5c3pncLJPFa8SuVm23AP4tft6mzPCL5at3I9M/edit

Specification

Specification link

Status: Specification being incubated in a Community Group

Status in Chromium

Blink components: Blink>Network>StreamsAPI

Implementation status: Enabled by default (tracking bug)

Consensus & Standardization

• Firefox: No signal
• Safari: Positive
• Web Developers: Positive

Owners

• ricea@chromium.org
• yhirano@chromium.org

Intent to Prototype url

Search tags

Last updated on 2021-12-13