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
It seems like the websockets code (when in single threaded mode) sits inside it's own loop and doesn't service any of the other HTTP requests. Is this correct, or did I miss something in how to call the code?
How hard would it be to change it so that it returns to the main poll loop between websocket messages?
The text was updated successfully, but these errors were encountered:
It should be possible, but the event loop has no support for write epoll, so would block writing. Which is much better than blocking reading and writing.
If you manage to get a patch working, I will be glad to merge it.
It seems like the websockets code (when in single threaded mode) sits inside it's own loop and doesn't service any of the other HTTP requests. Is this correct, or did I miss something in how to call the code?
How hard would it be to change it so that it returns to the main poll loop between websocket messages?
The text was updated successfully, but these errors were encountered: