On Wed, 2007-10-10 at 02:56 -0700, est wrote: > Thank you Christoph. > > Yes I have tried a independent daemon, but that's a bit complicated > for a small site. Is there a simipler way?
There is no guarantee that any Django process is going to be long running or only called once -- there will be repeated imports and restarts over the lifetime of the server. Both of these things mean that trying to control a single long-running process from something that runs as a response to Django imports or a request is going to have design problems. So you are trying to solve your problem in a way that is going to have a lot of problems in the future. Django handles the request/response driven side of your website or application. Long running processes, scheduled processes, offline processes -- all of these things should be managed separately, often via a daemon as suggested earlier. Trying to force control into Django really is going to be more pain that it's worth. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
