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