<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>I'm unsure why oslo.messaging would have a concepts of tasks. I didn't think it did.</div>
<div><br>
</div>
<div>Other projects building on-top of oslo.messaging imho should have a concept of tasks, oslo.messaging should seem like it should provide a reliable messaging layer.</div>
<div><br>
</div>
<div>Wondering why u think this should be coupled with oslo.messaging?</div>
<div><br>
</div>
<div>Taskflow[1] in particular has some of these semantics and it will use oslo.messaging when oslo.messaging achieves py3 compat.</div>
<div><br>
</div>
<div>[1] http://docs.openstack.org/developer/taskflow/</div>
<div><br>
</div>
<div>-Josh</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>John Wood <<a href="mailto:john.wood@RACKSPACE.COM">john.wood@RACKSPACE.COM</a>><br>
<span style="font-weight:bold">Reply-To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Thursday, April 24, 2014 at 11:58 AM<br>
<span style="font-weight:bold">To: </span>"<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>[openstack-dev] [oslo] [messaging] Curious about retry/scheduled tasks<br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div dir="ltr"><style type="text/css" id="owaParaStyle"></style>
<div fpstyle="1" ocsi="0">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">Hello folks,
<div><br>
</div>
<div>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. </div>
<div><br>
</div>
<div>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. </div>
<div><br>
</div>
<div>Thanks,</div>
<div>John</div>
<div><br>
</div>
</div>
</div>
</div>
</blockquote>
</span>
</body>
</html>