Thanks every one, and yes, I'm heaving problem with the project in production... I'm using fstcgi and nginx, and when it's called that view it just don't run in background, or run once and then it's stops...
So I'm thinking of using django-celery... but just have one more question... Javier, you said that with celery you can use the @task thing ins't it? But to make the celery work in the production I need to make some crazy confs in a virtualhost to it work? Or just use the @task + manage.py? (I still have hope that it's stupid easy as that to use it xD). Thanks! Em terça-feira, 20 de março de 2012 12h01min47s UTC-3, Javier Guerra escreveu: > > On Tue, Mar 20, 2012 at 9:52 AM, Arruda > <felipe.arruda.pontes@gmail.com<felipe.arruda.pon...@gmail.com>> > wrote: > > But I still wanted to know how to use the celery in this case =/ > > the idea is to use a Queue: > > you have a separate process (typically implemented in a manage > command) that stays running, and waits for messages in the queue. > > when the web app wants to do some slow processing, writes any needed > parameters to the queue and returns with a 'wait...' message > > the background process receives the queue item and does the process > without tying up the web response. > > > the first implementation almost everybody does is called "Ghetto > queues", it consist of writing the parameters to the database in a > 'todo' table, and a cron process that periodically checks these todo's > and processes them. it works, but falls down at a certain load. > after that, you need a real queue manager; either RabbitMQ, Redis > Queues, or a lot of other options. > > Celery is a python package that allows you to simply add a '@task' > decorator to any function; so that when you call them, they're not > executed, but instead the argument list is pushed to a queue. it also > creates an admin command that does the queue reading and actually > calls the functions with the arguments it founds on there. > > -- > Javier > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/eHejT5-eTHQJ. To post to this group, send email to django-users@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.
