Embrace the OS. Whats wrong with OS specific tools anyway? If you are developing on windows and deploying to unix then you can use something like cygwin to get cron in there.
When I code in java I use the excellent quartz scheduler, but then I have to use my home-gronw monitoring tools to ensure that its working. When I code in Python I can use cron and let the sysadmin deal with failed jobs, he has to watch a bunch of other crons anyway. But although it is easier to deploy django in a single self-contained app I would look to the OS to give you what it can. It may save you some headaches later. There are 2 types of scheduled processes though - ones based on clock time (like running the credit card transactions at 11:59) and ones based on application performance (like cleaning the cache or sessions) For timely events (like billing) I would stick to the most reliable and monitorable scheduling tool that you have. For other apps the signals trick or other 'in-process' systems will work. I recently helped a friend debug a PHP app where his in-process RSS scraper has a suble bug that was bringing the server to its knees. I was just having this debate with the java folk and I have seen it as almost a cultureal thing. I *like* the fact that python sits close to the OS, and I *like* the fact that java is completely hosting in its own library rich VM. Then again when I develop in MS I *like* Visual Studio and I *like* MSSQL. (When doing python or java I am free to dislike MSSQL though) As the previous email said: Just a thought, anyways. -Aaron --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
