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
As sub conf is rolled out across most exchanges now, the next steps are unfication with other subsystems. Currently engine's syncer will assume it can fetch ticker/orderbook data from websocket if it's enabled, when I could've disabled ticker/orderbook fetching in the exchanges sub conf. Same goes for per asset sub confgs. If I set websocket to enabled, ticker websocket streaming only for spot instead of all, then the syncer should use REST for the other assets and vice versa. In these cases the syncer will timeout due to no data and failover to REST
The text was updated successfully, but these errors were encountered:
New Issue
As sub conf is rolled out across most exchanges now, the next steps are unfication with other subsystems. Currently engine's syncer will assume it can fetch ticker/orderbook data from websocket if it's enabled, when I could've disabled ticker/orderbook fetching in the exchanges sub conf. Same goes for per asset sub confgs. If I set websocket to enabled, ticker websocket streaming only for spot instead of all, then the syncer should use REST for the other assets and vice versa. In these cases the syncer will timeout due to no data and failover to REST
The text was updated successfully, but these errors were encountered: