Takeshi Yoshino
Takeshi Yoshino
It depends on the internal state and the input, but when a new chuck is written to a CompressStream, the CompressStream may have 2 choices, buffering some input bytes until...
/cc @yutakahirano ReadableByteStream has been merged into ReadableStream interface. It's time to update the ReadableStream section of the Fetch spec (https://fetch.spec.whatwg.org/#readablestream) to adopt the updated ReadableStream and construct a ReadableStream...
/cc @sicking @domenic A separate thread to continue discussion started at https://github.com/whatwg/streams/issues/97#issuecomment-60809227.
#698 indicated that our BYOB respond logic might be not sound enough regarding various states about reader existence/type. Need to review the logic.
Potential targets of optimization - TextEncodingTransformByteStream - IdentityTransformByteStream - BufferingTransformByteStream - ByteCountingIdentityTransformByteStream - The wrapper is not a pure identify transform but with observation functionality. - In https://github.com/yutakahirano/fetch-with-streams/issues/37#issuecomment-105512434, use of...
I started feeling that we've been too optimistic about use of specialized `pipeTo()` algorithm given an identify transform between the pair of rs/ws. In the discussion about the `Request` object,...
https://github.com/http2/http2-spec/pull/323
http://http2.github.io/http2-spec/index.html#ConnectionHeader So, maybe we can do some rewrite such as this paragraph: > A server SHOULD send a SETTINGS frame as soon as possible whether it supports other schemes or...
It's kinda bikeshed. But 101 might not be the right status to use for WebSocket over HTTP/2.0 as we're not switching from anything but just starting WebSocket. Assuming that all...