Websockets for Django applications using Redis as message queue
Project home: https://github.com/jrief/django-websocket-redis
Detailed documentation on ReadTheDocs.
Online demo: http://django-websocket-redis.awesto.com/
This module implements websockets on top of Django without requiring any additional framework. For
messaging it uses the Redis datastore and in a production environment, it is
intended to work under uWSGI and behind NGiNX
or Apache version 2.4.5 or later.
./manage.py runserver
.If unsure, if this proposed architecture is the correct approach on how to integrate Websockets with Django, then
please read Roberto De Ioris (BDFL of uWSGI) article about
Offloading Websockets and Server-Sent Events AKA “Combine them with Django safely”.
Please also consider, that whichever alternative technology you use, you always need a message queue,
so that the Django application can “talk” to the browser. This is because the only link between the browser and
the server is through the Websocket and thus, by definition a long living connection. For scalability reasons you
can’t start a Django server thread for each of these connections.
Refer to changelog.rst
Please use the issue tracker to ask questions.
Copyright © 2015 Jacob Rief.
MIT licensed.