Introducing Flask-Sockets(kennethreitz.org)
kennethreitz.org
Introducing Flask-Sockets
http://kennethreitz.org/introducing-flask-sockets/
7 comments
> (And in practice I don't think you would want to deploy on anything besides Gunicorn.)
(You should definitely have a look at uWSGI.)
(You should definitely have a look at uWSGI.)
I have been running uWSGI for many years, I only recently made the switch to Gunicorn for the async gevent/websockets support.
(The last time I looked, which was a few months ago anyway, uWSGI support for gevent/websockets wasn't very robust.)
(The last time I looked, which was a few months ago anyway, uWSGI support for gevent/websockets wasn't very robust.)
This looks like a thin wrapper over gevent-websocket. The code is slightly longer than the README: https://github.com/kennethreitz/flask-sockets/blob/master/fl...
Not to discredit the attempt to make gevent-websocket more accessible, but there's nothing really new here. Here's an example of using gevent-websocket with flask without this library: https://gist.github.com/lrvick/1185629
Not to discredit the attempt to make gevent-websocket more accessible, but there's nothing really new here. Here's an example of using gevent-websocket with flask without this library: https://gist.github.com/lrvick/1185629
When used in conjunction with Gunicorn, this setup gets significantly more complicated, involving middlewares and monkeypatches. That's why I wrote the module :)
This also doesn't require the use of Gevent, like using gevent-websockets directly does. Anything that inserts `wsgi.websocket` into the WSGI environ will suffice here.
This also doesn't require the use of Gevent, like using gevent-websockets directly does. Anything that inserts `wsgi.websocket` into the WSGI environ will suffice here.
Websockets in python is easy.
http://www.tornadoweb.org/en/stable/websocket.html
http://www.tornadoweb.org/en/stable/websocket.html
On top of that, tornado has built-in support for multiprocessing, so you can forego gunicorn as well: https://gist.github.com/jholster/2290574
Tornado is an excellent choice for websockets, but someone shouldn't have to switch web frameworks just to support them. This works well for people who like working with Flask and have existing applications that they want to add websocket support to.
Yep, totally get it. Just want to make sure people know about tornado as an option for greenfield projects.
Flask users will be grateful for support of web-sockets, because beginner in python can use flask & now flask-sockets too for building small but useful projects.
Thanks Reitz for this.
I've been using gevent-socketio for websockets with Flask. I'm new to python. Can someone tell me why I'd want to use this over gevent-socketio?
A few questions, does this work with Python 3.3?
Also, how is it better than Tornado web sockets?
Also, how is it better than Tornado web sockets?
Unfortunately it looks like Gevent still has issues with Python 3:
https://github.com/surfly/gevent/issues/38
You can check Python 3 support for major packages at: https://python3wos.appspot.com
https://github.com/surfly/gevent/issues/38
You can check Python 3 support for major packages at: https://python3wos.appspot.com
Why does something have to be better to be useful?
Python 3 compatibility was my first question also.
Unfortunately this relies on gevent and gevent does not work on py3.
Unfortunately this relies on gevent and gevent does not work on py3.
I was kind of hoping this would be some sort of power socket shaped like a pocket flask.
However, based on my testing, in its current state it's nowhere near ready for production. There are some serious bugs relating to memory leaks, improperly closing stale sockets, and deployment on Gunicorn with # workers > 1 is not currently possible. (And in practice I don't think you would want to deploy on anything besides Gunicorn.) The project also seems to be somewhat inactive, there are a lot of open critical issues and there hasn't been any real activity in the last 6 months or so.
At this point I am considering removing the library and using a straight websocket implementation with a simpler protocol instead.