Flask, Flask-Login and Socket.io: Keep a session active even when not sending requests
Date : March 29 2020, 07:55 AM
like below fixes the issue Interesting problem.
Unfortunately session access in a Socket.IO event is not bi-directional. You can get the contents of the session, but you cannot make modifications, since the entire Socket.IO session occurs within a single WebSocket request, making it impossible to send an HTTP response with the session updates.
|
Python heroku configure procfile gunicorn + gevent for socket.io chat app | RuntimeError: You need to use the gevent-web
Date : March 29 2020, 07:55 AM
Does that help The error is correct, you need to use the gevent-websocket webserver and not the native gevent web server that comes with gunicorn. It seems you are searching for answers all over the place. I would suggest that you use the Flask-SocketIO documentation as the ultimate source of truth, as I keep that updated. gunicorn -k geventwebsocket.gunicorn.workers.GeventWebSocketWorker -w 1 module:app
|
Gevent/Gevent-websocket not being used by Flask-SocketIO
Date : March 29 2020, 07:55 AM
I wish this helpful for you The portion of the docs that you quoted refers to the async_mode argument, and how it is set by default. You are setting async_mode='threading', so that disables the automatic selection of an async mode. Remove the argument, and then you'll get eventlet or gevent, depending on what you have installed.
|
Socket.io handler using Gevent / Tornado & Flask
Date : March 29 2020, 07:55 AM
|
Which setup is more efficient? Flask with pypy, or Flask with gevent?
Date : March 29 2020, 07:55 AM
|
Boards Message :
Related QUESTIONS :