On 07 Mar 2014, at 01:41, Sandy Walsh <sandy.wa...@rackspace.com> wrote:
> Which is why modelling this stuff in code is usually always better and
> why I'd lean towards the TaskFlow approach to the problem. They're
> tackling this from a library perspective first and then (possibly)
> turning it into a service. Just seems like a better fit. It's also the
> approach taken by Amazon Simple Workflow and many BPEL engines.
In case of Amazon SWF it works in the opposite way. First of all it’s a
language agnostic web service, then they have language specific frameworks
working on top of the service.
As for callbacks, I agree. And we keep it in mind as well.
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
