pangea
/
django-orchestra
7
0
Fork 0
Code Issues 1 Pull Requests 2 Packages Projects Releases Wiki Activity

Added mailer README file

This commit is contained in:
Marc Aymerich 2015-05-07 20:04:28 +00:00
parent 096d59f38d
commit 5c10c39157
2 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
orchestra/contrib/mailer/README.md Normal file
View File

@ -0,0 +1,5 @@
This is a simlified clone of [django-mailer](https://github.com/pinax/django-mailer).
Using `orchestra.contrib.mailer.backends.EmailBackend` as your email backend will have the following effects:
* E-mails sent with Django's `send_mass_mail()` will be queued and sent by an out-of-band perioic task.
* E-mails sent with Django's `send_mail()` will be sent right away by an asynchronous background task.

2
orchestra/contrib/tasks/README.md
View File

@ -1,5 +1,5 @@
This is a wrapper around djcelery and celery `@task` and `@periodic_task` decorators. It provides transparent support for switching between executing a task on a plain Python thread or This is a wrapper around djcelery and celery `@task` and `@periodic_task` decorators. It provides transparent support for switching between executing a task on a plain Python thread or
pushing the task on a queue (rabbitmq) and executing it on a Celery worker. the traditional way of pushing the task on a queue (rabbitmq) and wait for a Celery worker to run it.
A queueless threaded execution has the advantage of 0 moving parts instead of the alternative rabbitmq and celery workers. Less dependencies, less memory footprint, less points of failure. A queueless threaded execution has the advantage of 0 moving parts instead of the alternative rabbitmq and celery workers. Less dependencies, less memory footprint, less points of failure.