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 the high-level API MarketDataListener allows you to be notified on top of book refresh with providing the top level only (and not tracking depth), or full refresh providing the whole book and getting every update (also e.g. 5th level quantity change).
It would be quite useful to keep populating the whole book, but only get a callback when the top level (price or quantity) changed with a reference to the full book. This is a combination of subscribedToTop and subscribedToEntireBook of ImpliedBookHandler.
The text was updated successfully, but these errors were encountered:
I suppose the combination should be implemented as possible option. The idea of subscribedToTop to do not even spend a processing time if you need just top of the book in business logic. But yes, from application point of view, in case of high-level, an application probably requests current state of entire book and reacts to top of the book notifications ... So you are right in this case:-)
Currently the high-level API
MarketDataListener
allows you to be notified on top of book refresh with providing the top level only (and not tracking depth), or full refresh providing the whole book and getting every update (also e.g. 5th level quantity change).It would be quite useful to keep populating the whole book, but only get a callback when the top level (price or quantity) changed with a reference to the full book. This is a combination of
subscribedToTop
andsubscribedToEntireBook
ofImpliedBookHandler
.The text was updated successfully, but these errors were encountered: