-
Notifications
You must be signed in to change notification settings - Fork 766
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
Comments
your message will be in OS buffer, you can check it by command |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
The text was updated successfully, but these errors were encountered: