Thanks for the quick reply! I think I may go the Redis route since I'm already using it anyways.
Also, thanks for introducing me to Orbited/Morbid and STOMP. I've never heard of them. From a quick DuckDuckGo Search and some reading, STOMP reminds me a lot of Nathan Marz's Storm architecture/paradigm which was powerful and very pleasant to use (after the initial learning curve). I'll definitely play around with them in the future.
On Saturday, March 3, 2012 8:46:27 AM UTC-5, ojno wrote:
It's probably easier to send your progress messages some other way, in your database or e.g. Redis if you're using it. If your application is web-based, you could look into using Orbited/Morbid to send realtime progress messages to the browser via STOMP, avoiding the need for your 'main task' to keep running at all.
I know I can restructure my code to follow more of a functional paradigm as opposed to a procedural one to run it asynchronously but then I don't know how to grab the status information properly. Here's the general outline of what I'm following to pull that Progress data: http://ask.github.com/celery/userguide/tasks.html#custom-states
Does anybody have any suggestions on how to do this? Or should I just go synchronous and risk the deadlock problem?