Skip to main content

Websocket support for Django using Redis as message queue

Project description

Websockets for Django applications using Redis as message queue

This module implements websockets on top of Django without requiring any additional framework. For messaging it uses the [Redis](http://redis.io/) datastore and in a production environment, it is intended to work under [uWSGI](http://projects.unbit.it/uwsgi/) and behind [NGiNX](http://nginx.com/).

You can find detailed documentation on [ReadTheDocs](http://django-websocket-redis.readthedocs.org/en/latest/).

Features

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

  • Runs in a cooperative concurrency model, thus only one thread/process is simultaneously required to control all open websockets.

  • Full control over the main loop during development, so Django can be started as usual with ./manage.py runserver.

  • No dependencies to any other asynchronous event driven framework, such as Tornado, Twisted or Node.js.

  • The only additional requirement is a running instance of Redis, which by the way is a good replacement for memcached.

Build status

Currently, unit tests require a running Redis datastore, therefore they hav to run locally and can’t be deployed on Travis-CI.

Questions

Please use the issue tracker to ask questions.

License

Copyright (c) 2013 Jacob Rief Licensed under the MIT license.

Release History

  • 0.1.1 - instead of CLI monkey patching, explicitly patch the redis.connection.socket using gevent.socket

  • 0.1.0 - initial revision

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

django-websocket-redis-0.1.1.tar.gz (11.5 kB view hashes)

Uploaded Source

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page