Bootstrapping WebSockets with HTTP/2

[lyarbean]

Suppose a web page has a script to create a new websocket,
then every tab that loads that page (at each time) will create a new websocket.
In HTTP1.1, a websocket is in fact a TCP socket connection :-(.
And browsers like chrome and firefox limit number of websocket connections.

Bootstrapping WebSockets with HTTP/2, as specified by https://tools.ietf.org/html/rfc8441,
allow multiple websockets to live in one Http2 connection, as a stream, and already gets supported by chrome and firefox.

However the work to support Websocket in Cutelyst seems not easy.
I noticed that the design of http2 is far different from http's, which stop my steps:
For Http

1. ProtoRequestHttp is ProtocolData and EngineRequest
2. ProtocolHttp is Protocol
3. ProtocolWebSocket is Protocol

For Http2

1. H2Stream is EngineRequest
2. ProtoRequestHttp2 is ProtocolData
3. ProtocolHttp2 is Protocol

@dantti , I would greatly appreciate it if you have plan to support it. Thanks!

[dantti]

You can probably do that using nginx as the frontend, I'm leaning towards HTTP/3 rather than this specially since I don't use and didn't saw real benefits in H2, rather than a very complex code to deal with it.

[dantti]

Still doesn't seem so hard to implement it anyway, you basically has to extend the ProtoRequestHttp2 with the new settings, and H2Stream with websocket virtual functions probably using ProtocolWebSocket to read/write messages.

[lyarbean]

Still doesn't seem so hard to implement it anyway, you basically has to extend the ProtoRequestHttp2 with the new settings, and H2Stream with websocket virtual functions probably using ProtocolWebSocket to read/write messages.

Thanks, I got it. I will try later.