Re: [whatwg/streams] do chunk boundaries have to be preserved through to underlying sink? (#739)

When writing to a file or a network socket, large chunks are more efficient than small ones. But maybe we are more likely to do writev-style semantics than concatenating chunks inside WritableStream.

writev-style semantics are discussed in https://github.com/whatwg/streams/issues/27 along with a lot of discussion of cork. Personally I feel that cork is a niche use case compared to "please let me write all queued data in one go".

On the ReadableStream size, the source already has the ability to do appropriately-sized reads via `desiredSize`. So probably nothing to do there?

When `pipeTo()` is used it would nice if the underlying sink was able to simultaneously write all the data from the writable queue _and_ the readable queue. But I have no idea if that can be standardised in a sane way.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/streams/issues/739#issuecomment-297998447