David, Celery sounds really good, thanks for the tip, I'll have a deeper look into it as soon as I've got some time, if I can't get it up for this project I'll study it's details and put it up later maybe for a new release or a new project. For what I've seen until now it seems to be perfect, because you completly control the whole process, once a job has completed it even returns you a backtrace in case of failure or a success message. Only the setup/installation looks quite complex, one question: Is it capable of running on every web server that supports Python? or are there any other requirements or things to think about?
John your solution is very smart too, but sometimes it could cause some overhead, if I do actions while the user is offline or seeing another section, the user won't notice it, but if you do it inside a request the user may has to wait a little longer, it depends on the complexity of the operation you want to do. Brian & Creecode Django Custom management commands are really the same as this: from django.core.management import setup_environ import settings setup_environ(settings) or am I wrong? I'm just running the scripts with these three lines on top (even before the other import statements). The apscheduler looks like a good and simple implementation for A, thanks Guilherme. And finally Mateus the at(if it's available) command would be a very easy solution for A too. On 15 dic, 11:42, David De La Harpe Golden <david.delaharpe.gol...@ichec.ie> wrote: > Tim Daniel wrote: > > So how can I implement solution B? Is there a posibility to create a > >cronon a user action that executes only one time? > > > NOTE: I don't want to rely on a thread that should stay alive for two > > hours ore more inside the server memory. > > Well, celery uses a "celeryd" daemon process and a message queue, so > that is a thread staying alive om the server, but it's a completely > separate and manageable process from your web server: > > http://ask.github.com/celery/introduction.html > > It may look a little complex, but it really makes all sorts of long > running and scheduled tasks easy and well-integrated with django. > > FWIW, doing something two hours after someeventis basically a > one-liner:http://ask.github.com/celery/userguide/executing.html#eta-and-countdown -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
