--
You received this message because you are subscribed to the Google Groups "celery-users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/celery-users/-/bgeK_8_KPdIJ.
To post to this group, send email to celery...@googlegroups.com.
To unsubscribe from this group, send email to celery-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/celery-users?hl=en.
- ojno
To unsubscribe from this group, send email to celery-users+unsubscribe@googlegroups.com.
> 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.
>
If you can update the browser in real-time that is the best solution,
but you can also have each task return the result of its subtask(s) to traverse
the graph of dependencies and that by only having a reference to the first
result, see my answer in this thread:
https://groups.google.com/group/celery-users/browse_thread/thread/ccb2414bb044d3a8/cf27c05565f1d18a?lnk=gst&q=callback+state+propagation#cf27c05565f1d18a
--
Ask Solem
twitter.com/asksol | +44 (0)7713357179