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