Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Send asynchronous messages to users

branch: master

Fetching latest commit…

Octocat-spinner-32-eaf2f5

Cannot retrieve the latest commit at this time

Octocat-spinner-32 async_messages
Octocat-spinner-32 tests
Octocat-spinner-32 .gitignore
Octocat-spinner-32 .travis.yml
Octocat-spinner-32 AUTHORS
Octocat-spinner-32 LICENSE
Octocat-spinner-32 MANIFEST.in
Octocat-spinner-32 README.rst
Octocat-spinner-32 release.sh
Octocat-spinner-32 runtests.py
Octocat-spinner-32 setup.py
README.rst

django-async-messages

Simple asynchronous messages for django.

Questions

What problem does this solve?

Suppose a user instigates an expensive task that you are processing offline (eg using Celery). This library provides a simple mechanism for notifying the user when the task is finished, utilising Django's messaging framework.

What's an example?

You might use Celery to generate a large report and then employ this library to notify the user that their report is ready to be downloaded. The user will see the message you've sent them when they make their next request after the message is submitted.

How does it work?

A cache is used to persist the messages, and middleware is used to pick these up and submit them to Django's messaging framework. All very simple.

Aren't there other libraries that do this?

Yes, there are - but they solve the problem in different ways:

What's good about this implementation?

  • It's simple, fast and easy to use.
  • It works cohesively with existing Django cache and messages framework. It will work no matter what cache backend your are using, and whatever storage backend is used for messages.

What's bad?

  • A user may miss the message if they navigating quickly between pages. But this is a general problem of the Django messages framework.

Install

From PyPI (stable):

pip install django-async-messages

From Github (unstable):

pip install git+git://github.com/codeinthehole/django-async-messages#egg=djang-async-messages

Add 'async_messages.middleware.AsyncMiddleware' to your MIDDLEWARE_CLASSES. Ensure it comes after 'django.contrib.messages.middleware.MessageMiddleware'.

You need to have CACHES configured in you settings for this to work. As usual, memcache is the best choice.

Use

Send a message to a single user:

>>> from async_messages import message_user
>>> from django.contrib.auth.models import User
>>> barry = User.objects.get(username='barry')
>>> message_user(barry, "Barry, your report is ready")

Send a message to lots of users:

>>> from async_messages import message_users
>>> staff = User.objects.filter(is_staff=True)
>>> message_users(staff, "All budgets must be spent by the end of the day")

Specify message level:

>>> from django.contrib.messages import constants
>>> message_users(staff, "Boom!", constants.WARNING)

Send multiple messages to a single user:

>>> from async_messages import message_user
>>> from django.contrib.auth.models import User
>>> barry = User.objects.get(username='barry')
>>> message_user(barry, "Barry, your report is queued up for processing")
>>> # do more awesome stuff
>>> message_user(barry, "Barry, your report is ready")

Changelog

0.1.5

  • Added possibility to queue multiple messages

0.1.2

  • Altered dependency on Django to be only 1.2+

0.1.1

  • Altered middleware to use process_response.
  • Better docstrings

0.1

  • Minimum viable product
Something went wrong with that request. Please try again.