[Baypiggies] Asynchronous web tasks

[Ryan Matthew Balfanz]

I meant to reply sooner, and a few have already suggested celery, but I
wanted to through this in the mix.

The first example (
http://ask.github.com/celery/getting-started/introduction.html) says it
all. You can fire tasks from anywhere, such as in a view, or as a
signal receiver, etc. Periodic tasks (see
http://ask.github.com/celery/userguide/periodic-tasks.html) offer scheduled
jobs. I use both.

I think that the django-celery-email (
http://pypi.python.org/pypi/django-celery-email /
https://github.com/pmclanahan/django-celery-email) project is a great
starting point. Take a look at the code for a simple, yet powerful, example
which isn't much more complicated than the celery docs themselves.

I had the most trouble getting the task results to work in the admin, then
I found out about celerycam (
http://ask.github.com/celery/userguide/monitoring.html#starting-the-monitor),
which I manage with supervisor.

-Ryan

On Thu, Feb 2, 2012 at 9:36 AM, Tung Wai Yip <tungwaiyip at yahoo.com> wrote:

> I'm using RabbitMQ and Celery. It certainly can be triggered by both
> cases. In addition, you can deploy it on different servers if necessary.
>
> Wai Yip
>
>
>  I use Django in production and now have a need to perform asynchronous
>> backend tasks that
>> a. Are some scheduled jobs
>> b. Jobs triggered via a user input via Django frontend.
>>
>> I have been thinking of using twisted or message queues (RabbitMQ and
>> celery) to achieve this.  From my research so far:
>>
>> 1. Twisted allows both a and b though the learning curve with twisted is
>> steeper
>> 2. RabbitMQ and celery is easier to use, allows a but does it also allow
>> b?
>>
>> I am looking for some opinions /recommendations to use one of  these two
>> technologies or something else altogether ?
>> Thanks
>> Meenal
>>
> ______________________________**_________________
> Baypiggies mailing list
> Baypiggies at python.org
> To change your subscription options or unsubscribe:
> http://mail.python.org/**mailman/listinfo/baypiggies<http://mail.python.org/mailman/listinfo/baypiggies>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/baypiggies/attachments/20120203/9142e632/attachment.html>