Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Market data subscription logic #16

Open
jheusser opened this issue Mar 15, 2017 · 1 comment
Open

Market data subscription logic #16

jheusser opened this issue Mar 15, 2017 · 1 comment

Comments

@jheusser
Copy link
Contributor

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.

@iamolever
Copy link
Contributor

iamolever commented Mar 15, 2017

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:-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants