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

Question: Does Websocket buffer messages that not processed? #987

Open
alm0ra opened this issue May 12, 2024 · 2 comments
Open

Question: Does Websocket buffer messages that not processed? #987

alm0ra opened this issue May 12, 2024 · 2 comments

Comments

@alm0ra
Copy link

alm0ra commented May 12, 2024

Consider a scenario where I'm operating entirely synchronously, subscribed to multiple channels, and receiving messages at a rapid pace. However, my message processing capability lags behind the rate at which messages are generated. In such a situation, will I eventually receive older messages, or does the WebSocket client discard them? Moreover, is there a way to instruct the WebSocket client not to retain a buffer?

@alm0ra
Copy link
Author

alm0ra commented May 12, 2024

@liris

@yaroshoris
Copy link

your message will be in OS buffer, you can check it by command
netstat -npt | grep python --- to check incoming buffer
about "instruct the WebSocket client not to retain a buffer" - It seems that websocket-client doesn't handle it, you can create a workaround solution in your code to load all buffered messages and discard some of them.

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

2 participants