We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Is your feature request related to a problem? Please describe. When using emit with callbacks if the other party frequently disconnects and misses events, the callbacks in base_manager.py (https://github.com/miguelgrinberg/python-socketio/blob/main/src/socketio/base_manager.py#L15) will just keep growing over time.
emit
callbacks
base_manager.py
Describe the solution you'd like Implement optional timeout on emit, as described here https://socket.io/docs/v4/emitting-events/#with-timeout
Describe alternatives you've considered I can use call instead of emit but I have to wrap that in an async runtime...
call
The text was updated successfully, but these errors were encountered:
A call() is a pythonic version of the emit with timeout. If you don't want to block then you can run it in a background task.
call()
But in any case, the accumulation of callbacks that never trigger should be addressed. I'll think about how to handle that.
Sorry, something went wrong.
miguelgrinberg
No branches or pull requests
Is your feature request related to a problem? Please describe.
When using
emit
with callbacks if the other party frequently disconnects and misses events, thecallbacks
inbase_manager.py
(https://github.com/miguelgrinberg/python-socketio/blob/main/src/socketio/base_manager.py#L15) will just keep growing over time.Describe the solution you'd like
Implement optional timeout on emit, as described here https://socket.io/docs/v4/emitting-events/#with-timeout
Describe alternatives you've considered
I can use
call
instead ofemit
but I have to wrap that in an async runtime...The text was updated successfully, but these errors were encountered: