SummaryThe 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().
Link to “Intent to Prototype” blink-dev discussionhttps://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/P97xJm1TFj4/PA0FKwLhBwAJ
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?Yes. This feature is purely implemented in Blink and so cross-platform support is automatic.
Is this feature fully tested by web-platform-tests?Extensive web platform tests are under review at https://github.com/web-platform-tests/wpt/pull/24546.
Link to entry on the Chrome Platform Statushttps://chromestatus.com/feature/5298733486964736
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAC_ixdyr9icisrjJiP7zja7MAGOjdCaY7GrVSvnpHBB0Vc_Y2A%40mail.gmail.com.
On Tue, Aug 18, 2020 at 11:32 AM Adam Rice <ri...@chromium.org> wrote:Those requests are fairly recent. At the same time, since this is now part of a WHATWG spec, I'm assuming that there was multi-engine interest. Is that a correct assumption?
Aside: Would be good to highlight the bits directly related to transferable streams in the explainer. As is, it's hard for someone unfamiliar with Streams to understand the examples from the explainer alone.
It's unclear what's the feature detection story here.
Would the code examples work in browsers that haven't yet shipped transferable streams? (I'm guessing no, but want to confirm)
Can developers know that the feature is not supported?
Would they need to care in the future when transferable streams enable zero copy object transfers? (e.g. maybe transfer large objects only when no copy is involved)
Those requests are fairly recent. At the same time, since this is now part of a WHATWG spec, I'm assuming that there was multi-engine interest. Is that a correct assumption?
This seems like an early review. Did a more thorough review happen?
Hi Adam, did you have a response on this question also? Thanks.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAC_ixdzF2_XbPWYE1nqC6k05D1-XEQ1VVVgytKbdUaZayiZczQ%40mail.gmail.com.