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
Currently we are doing all the node requests using HTTP. That means for every request our backend has to do another HTTP handshake. Alternatively we could also consider using web sockets. With those we only have to do a single handshake on system start and therefore reduce a bunch of latency caused by these handshakes.
But maybe more importantly it seems that the support for websockets might be better in the eco system than the support for plain HTTP requests.
Details
We should add support for web sockets RPC URLs. To remain flexible in case we encounter issues with WS we should still support using HTTP URLs. Maintaining both should be no issue because there is barely no active development on those protocol components.
Acceptance criteria
We should be able to replace all http:// RPC URLs with ws:// URLs.
The text was updated successfully, but these errors were encountered:
Background
Currently we are doing all the node requests using HTTP. That means for every request our backend has to do another HTTP handshake. Alternatively we could also consider using web sockets. With those we only have to do a single handshake on system start and therefore reduce a bunch of latency caused by these handshakes.
But maybe more importantly it seems that the support for websockets might be better in the eco system than the support for plain HTTP requests.
Details
We should add support for web sockets RPC URLs. To remain flexible in case we encounter issues with WS we should still support using HTTP URLs. Maintaining both should be no issue because there is barely no active development on those protocol components.
Acceptance criteria
We should be able to replace all
http://
RPC URLs withws://
URLs.The text was updated successfully, but these errors were encountered: