I actually started writing a queueing system a while back (and lost it during a hard drive crash)
I recommend you look at hugo's stuff.jobcontrol package https:// simon.bofh.ms/django-projects/stuff/trunk/jobcontrol/ as a base. regards Ian On 09/07/2006, at 6:07 PM, wiz wrote: > > On 7/6/06, Tyson Tate <[EMAIL PROTECTED]> wrote: >>> Why not put the messages in the database and read it from other >>> side? > >> I'm not sure I understand what you mean. Do you mean that I should >> take the API call responses and read them from the user-side with >> AJAX? I hope that's not what you meant because that would just be >> silly. :) > Instead of directly polling services, your signals may put an entry in > a table like 'ping magnolia for user A, get 10 latest stufflets'. And > there are daemon (or process, hooked on cron), which will check his > queue table and do jobs. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
