Look into using a queue system of some form. Django-queue-service (http://django-queue-service.googlecode.com/) was developed to enable this but there's similiar mechanisms in use through many sites. Either developed internally, or using heavier-duty queuing mechanisms.
-joe On Mon, Jul 7, 2008 at 12:02 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Certain events require another operation to run. But it doesn't need > to happen immediately. > > I'm curious what people use for message passing / job queuing. > > Right now, I run cronjobs that run routine background processes, but > also some operations which should really be event driving. > > I was thinking that a piece of middleware could record a call to make > (and objects / parameters to pass) AFTER the view returned. This way, > you wouldn't need to schedule another process, and the job could > benefit from the full context. > > Can anyone scope this task for me? How hard would it be to make such a > middleware module? Where is a good place to start in writing a > middleware module? > > Thanks, > Ivan > tipjoy.com > > > --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
