Gábor Molnár

It was specified in the -07 draft, so this is not blocked anymore.

It's not clear how it should work... waiting for spec change.

The related http2-spec issue is this: https://github.com/http2/http2-spec/issues/18

It's now specified in the latest draft. It was decided that it is not supported in HTTP2 so it should throw an error or sometinhg. http://tools.ietf.org/html/draft-ietf-httpbis-http2-07#section-8.1.1

First of all, thanks for doing this benchmark! I didn't do any memory profiling yet, but I believe this should be a problem in node-http2 itself (and not some config...

Yeah you're right they are not deleted. The reason behind that is that streams still should react to frames after they becomes CLOSED, and currently this is implemented by keeping...

How about implementing this in the http2-protocol module: - if the Connection object receives an end of stream signal (basically a `connection.write(null)`) and `this._closed === false` (there was no normal...

Thanks, I'll try to review it ASAP, probably on the weekend!

Hi Mark, it's somewhat more complicated with node-http2 than http1 but it's doable. We have a `protocol` "submodule" that exposes the lower level building blocks of node-http2. Two such building...

Yeah the only issue is that node-http2 has a different class (and because of this, different proto for instances) for requests and responses than the built-in HTTP1 implementation. Express changes...