On Jul 6, 2006, at 12:07 AM, Malcolm Tredinnick wrote: > This sort of problem is why, when you brought this solution up last > month, a couple of us were still recommending doing this with cron or > some other system-level process, rather than hooking it into Django: a > transient process for handling a web request is not really a nice > place > to be doing long-running periodic tasks.
Because at the time, I didn't think Bluehost would let me run cron jobs (turns out they do). In the end, doing it the "hard way" turned out to be a good exercise in using signals and the dispatcher, which I think is one reason I followed through with it even after I found out that I can, indeed, run cron jobs with Bluehost. Dealing with forking etc. is definitely on the messy side of things. And really, to hook it up to cron instead is a snap because I'm already using signal-driven methods - I just raise the signal through a cron job instead of when the front page is loaded. This makes the project a little more portable, as well, which could come in handy someday, I guess. -Tyson --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
