23732 2013-11-05 18:50:44 +0000 Consider adding best-effort scatter/gather mode 2013-12-05 19:33:32 +0000 1 1 1 Unclassified WebAppsWG Streams API unspecified All All RESOLVED FIXED P2 normal --- 1 tyoshino tyoshino mike public-webapps public-webapps-bugzilla oldest_to_newest 95826 0 tyoshino 2013-11-05 18:50:44 +0000 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. 95971 1 tyoshino 2013-11-07 19:27:28 +0000 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. 96025 2 tyoshino 2013-11-08 08:23:25 +0000 (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 96240 3 tyoshino 2013-11-13 19:32:05 +0000 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. 97208 4 tyoshino 2013-12-05 19:33:32 +0000 Preview ver merged into ED.