OK, thanks for your reply. Both possible solutions you propose are 'polling' solutions. The first is triggered by a in-memory object (a running process), the second by a user-request. I'm interested in the first solution since I can't wait for a user-request before checking for scheduled events. This brings me to the problem of running a thread from within Django that checks the database once in a while. Unlike servlets that are run by their container when deployed, the python code in Django is only run after a user-request. I could make a view that initializes the application and link a url to that view that you have to visit before starting the application, but that feels a little awkward.
Is this solvable with Django, or am I using the wrong framework for my problem? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
