TODO: Implement the HTTP/3 layer

[jasnell]

The HTTP/3 layer will involve use of nghttp3 and an additional set of specializations for the native QuicSession/QuicClientSession/QuicServerSession/QuicStream classes. Work on this will begin in early September.

[jasnell]

Depends on #83 landing first

[Justsnoopy30]

(Early September passed a month ago)

[jasnell]

Indeed it did and work has started.

[Justsnoopy30]

Ok. Is it usable at this point yet?

[Justsnoopy30]

By usable, I mean I can run a nodejs http/3 website that serves a page, and Chrome Canary with experimental http/3 support enabled can access the website and see the page.

[jasnell]

Not yet. The underlying ngtcp2 library changed a number of the APIs relating to the tls handshake that assume the use of the BoringSSL QUIC apis that have not yet landed in OpenSSL 3. Given that we're using OpenSSL 1.1.1 and need to port those APIs, it's taking a bit longer to get completed.

[Justsnoopy30]

Ok.

[trivikr]

My experiments with running QUIC in Node.js, and loading website from Chrome will be documented at https://github.com/trivikr/node-http-servers#quic-server

[jasnell]

Basic http3 implementation is in. Not completed 100% but operational.