Hello folks, I am curious if olso.messaging exposes a means to support retry and defer semantics for tasks. For example, it could be nice to retry processing a failed task under some circumstances, such as if a network service is temporarily unavailable. It might also be beneficial to be able to run a task at a time in the future, or on a recurring basis such as to drive an asynchronous polling process.
These features can be handled in application code or orchestration services of course, but just curious if olso.messaging provides a lower-level mechanism for handling this. Thanks, John
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
