Thanks for all your replies guys, yes you're right - there are better tools for this job (we're looking at celery) but that only increases the number of moving parts for something fundamentally very simple.
Using a message broker like RabbitMQ makes our chain look like: nginx queue -> paster queue -> celery queue -> worker process Why so many queues and so many processes (and config files) to manage? All we really need is just to receive a request, return "200 OK" and start working on it. There is no "GUI", no browser, just a series of HTTP POSTs that don't expect anything in return. I hope this explains my thought process better! :-) Anyway, the issue is closed, thanks. -- ev -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en.
