yosh

For HTTP2, things got a little more awkward. The HTTP2 code isn’t built to have consuming a net.Socket as a fast path; 18/

HTTP2, like TLS, assumes a C++-backed socket and directly connects to it. But TLS is already there, so we have a Duplex-to-C++ wrapper: 19/

The (internal) JS class is called `StreamWrap`, and the corresponding C++ handle class is called `JSStream`. 20/

The idea is that a `StreamWrap` looks like a `net.Socket` in every way, bc it is also backed by a C++ handle with the same interface; 21/

The only difference is that instead of the wiring going into libuv, it goes to make calls back into the JavaScript streams methods. 22/

So, what I did for HTTP2 is similar to what TLS already does: If it’s not a Socket, wrap it w StreamWrap; and either way, attach to C++. 24/