django-websocket-redis 0.5.1

Websocket support for Django using Redis as datastore

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.

New in 0.4.5

• Created 1 requirements file under examples/chatserver/requirements.txt.

• Renamed chatclient.py to test_chatclient.py - for django-nose testrunner.

• Migrated example project to django 1.7.

• Edited docs/testing.rst to show new changes for using example project.

• Added support for Python 3.3 and 3.4.

• Added support for Django-1.8

• Removes the check for middleware by name.

Features

• Largely scalable for Django applications with many hundreds of open websocket connections.

• Runs a seperate 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 seperate 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 seperate main loop through Redis which, by the way is a good replacement for memcached.

• Optionally persiting 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.

Build status

Questions

Please use the issue tracker to ask questions.

License

Copyright © 2015 Jacob Rief.

MIT licensed.