On Wed, Oct 21, 2009 at 9:49 AM, Michael Thon <mike.t...@gmail.com> wrote: > Thanks for pointing me towards celery. Its probably overkill for what > I want to do right now but I'm going to try to set it up anyway.
the roll-your-own alternative is just setting a DB table with the queued tasks, and a cron job (or a long-running daemon) that fetches the next job from the table to work on it. it's called 'Ghetto queues'. it works and for small setups can be much ligther, but for complex, or high-speed, or critical availability, it can quickly become a nightmare to set up right. note that if you write the cron job in Python, you can easily import Django's ORM to make really easy to share data with the webapp AFAIK, the 'Queue' module you mention gets it mostly right; but works only on a single Python interpreter. If i'm not wrong, it can't mediate between the webapp and the background job, unless you modify either mod_wsgi or flup to spawn a thread for background processing.... (Graham? what would it take to add that to mod_wsgi?) -- Javier --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
