You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
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
The text was updated successfully, but these errors were encountered: