This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Best-effort scatter/gather mode, maybe as readType of e.g. "arraybuffer/sg" for "arraybuffer", relaxes the requirement that "readPromise is fulfilled with one object of the specified type" and allows fulfilling with fragments. This would be useful for performance sensitive apps since Stream implementation can choose to keep the original until right before fulfilling readPromise, and if it's set to "*/sg" type, just return an Array of the fragments without doing concat/split as possible. Best-effort means that it's not guaranteed that everything is kept as-is. Concat/split may happen.
Seems we don't need this. Once read is split into read and readExact and make read method sync/async hybrid, we can receive fragments without post tasking cost.
(In reply to Takeshi Yoshino from comment #1) > Seems we don't need this. Once read is split into read and readExact and > make read method sync/async hybrid, This is discussed at this bug. https://www.w3.org/Bugs/Public/show_bug.cgi?id=23772
Done in preview ver. https://dvcs.w3.org/hg/streams-api/raw-file/tip/preview.html Implementations can choose to delay serialization, split and concatenation as much as possible.
Preview ver merged into ED.