[Feature] Websocket Support For Triple Protocol

[oxsean]

Background

The Triple protocol is based on HTTP/2 and implements bidirectional communication using streams. WebSocket's long connection and event features are very suitable for RPC scenarios, so we consider using WebSocket as the communication layer for Triple, giving users more options.

In terms of specific implementation, we do not want to change the existing Triple protocol but rather adapt the Triple frame model to WebSocket frames. This can be done by referencing the approach used in HTTP/3.

Next Step

high-level design

[oxsean]

If you are interested in this, please leave a message to participate. However, implementing a new communication layer is quite challenging, so it is best if you have extensive experience with Netty

[finefuture]

I'm interested. Please assign it to me.

[finefuture]

Adapt the websocket frames model to the http2 frames, reuse the request processing flow of http2.

Extend the Endpoint and MessageHandler of javax.websocket, adapt the websocket on netty request processing model.