Re: [w3ctag/design-reviews] TAG Review Request: RTCQuicTransport (#303)

To counter the arguments against streams:

1. One could implement the currently proposed read/write API on top of the streams API. They are just as low level (if you want them to).
2. Streams allow implementations to optimise the data flow when piping from an internal source to an internal sink (e.g. piping an HTTP response to a QUIC stream) or when applying internal transform streams (that are exposed).
3. The API of streams potentially reduces copying with the BYOB concept by writing data directly into the provided buffer whereas the currently proposed API provides no way to achieve that.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/303#issuecomment-422196279