Websockets for Django applications using Redis as message queue
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
Vasilii T e7477f49df
Merge pull request #1 from DaniilSezonov/master
2 years ago
docs Bump to version 0.5.2 3 years ago
examples Merge pull request #263 from charleswhchan/update-examples 3 years ago
stress-tests Import gevent.socket 7 years ago
ws4redis Refactoring for Django minor versions. 2 years ago
.gitignore update example project 6 years ago
.travis.yml always use manage.py migrate 3 years ago
LICENSE.txt Initial revision 8 years ago
MANIFEST.in Added static files 7 years ago
README.md Remove What's New and link to changelog.rst 3 years ago
TODO.txt update example project 6 years ago
setup.py attempt to run tests with Python 3.4-3.6 3 years ago

README.md

django-websocket-redis

Project home: https://github.com/jrief/django-websocket-redis

Detailed documentation on ReadTheDocs.

Online demo: http://django-websocket-redis.awesto.com/

Websockets for Django using Redis as message queue

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.

Features

  • Largely scalable for Django applications with many hundreds of open websocket connections.
  • Runs a separate Django main loop in a cooperative concurrency model using gevent, thus only one thread/process is required to control all open websockets simultaneously.
  • Full control over this separate main loop during development, so Django can be started as usual with ./manage.py runserver.
  • No dependency to any other asynchronous event driven framework, such as Tornado, Twisted or Socket.io/Node.js.
  • Normal Django requests communicate with this separate main loop through Redis which, by the way is a good replacement for memcached.
  • Optionally persisting messages, allowing server reboots and client reconnections.

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.

Release History

Refer to changelog.rst

Build status

Build Status Downloads

Questions

Please use the issue tracker to ask questions.

License

Copyright © 2015 Jacob Rief.

MIT licensed.