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

Limit incoming data on websocket #17

Open
the-serious-programmer opened this issue Nov 24, 2021 · 3 comments
Open

Limit incoming data on websocket #17

the-serious-programmer opened this issue Nov 24, 2021 · 3 comments

Comments

@the-serious-programmer
Copy link

Our application heavily relies on:
https://github.com/bitvavo/node-bitvavo-api#book-subscription-with-local-copy

It would be awesome to have a configuration parameter that can limit the amount of data coming in, so that instead of 100+ bids and asks, for instance the top 10 for both can be returned on every book update. This to limit latency, network bandwith etc.

@StefanBloemheuvel
Copy link

Did you found a way to achieve this?

@the-serious-programmer
Copy link
Author

@StefanBloemheuvel unfortunately not, this cannot be solved without work on the bitvavo back-end (as the back-end has to send less data to the client).

@quixot1c
Copy link

If you only need the best bid and ask you can use the ticker subscription. Otherwise I guess you are out of luck.

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

No branches or pull requests

3 participants