DavidA wrote: > > Russell Blau wrote: > >>Ahh, thanks, it always helps to take the blinders off. The only downside is >>that I have to learn how to use yet another software package. ;-) > > > An alternative that stays inside Django is to setup a trigger in cron > (or NT's Task Scheduler) that gets a URL every few minutes and the view > code for that URL does the email processing you mention. You avoid > creating a true daemon/service just by "waking" up periodically and > doing any work that needs to be done. > > I use this technique for a scheduled task application written in > Django. It works well, avoids the threading issues, and in my case is > good enough for the problem at hand. >
This is a commonly used pattern in the Zope world (where I'm coming from). An advantage to doing it like this is that you can run your cronjob on a different box. -- Wade Leftwich Ithaca, NY --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
