Timothy Gu
Timothy Gu
@mde Already looking nice though. Nice job! :)
I would agree with the general sentiment expressed in the OP: that HTTP/2 should be provided transparently, like it is in browsers. The biggest *non-technical* challenge right now, is that...
@bitinn Compressed headers are still nice though.
> Should we assume it will be eventually as simple a matter as setting a flag and changing to a `require("http2")` line? No :( I don't think so, at least....
Yeah, I agree with the Agent thing. Connection pooling is substantially more well-defined for HTTP/2. But at the same time, an HTTP/2 connection is not stateless like an HTTP/1.1 connection...
> The ALPN negotiation seems fairly well documented for the Node HTTP/2 implementation as well. Only for the server side, unfortunately.
> Aren't the settings limited to connection-level settings though? Window size etc mostly for managing the correct bandwidth settings? Or are there other more stateful things to do with the...
I would prefer it all to be transparent, i.e. not add another dependency that does the same thing we can do in just a few lines. In nodejs/node#16256 Node.js seems...
@hthetiot We will not be using any HTTP/2 implementation other than the one in Node.js, when the Node.js used has HTTP/2 support.
@ThisIsMissEm There are nontrivial differences in the `stream.Readable` API vs. the web `ReadableStream` API, and using the constructors of the two classes the same way unfortunately doesn't work. See some...