<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Ok, got it.<div class=""><br class=""></div><div class="">So my general suggestion here is: let's keep it as simple as possible for now, create something that works and then let’s see how to improve it. And yes, consumers may be and mostly will be 3rd parties.</div><div class=""><br class=""></div><div class="">Thanks</div><div class=""><br class=""><div class="">
<div class="">Renat Akhmerov</div><div class="">@ Mirantis Inc.</div><div class=""><br class=""></div><br class="Apple-interchange-newline">
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On 09 Dec 2014, at 08:25, W Chan <<a href="mailto:m4d.coder@gmail.com" class="">m4d.coder@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Renat,<div class=""><br class=""></div><div class="">On sending events to an "exchange", I mean an exchange on the transport (i.e. rabbitMQ exchange <a href="https://www.rabbitmq.com/tutorials/amqp-concepts.html" class="">https://www.rabbitmq.com/tutorials/amqp-concepts.html</a>). On implementation we can probably explore the notification feature in oslo.messaging. But on second thought, this would limit the consumers to trusted subsystems or services though. If we want the event consumers to be any 3rd party, including untrusted, then maybe we should keep it as HTTP calls.</div><div class=""><br class=""></div><div class="">Winson</div><div class=""><br class=""></div></div>
_______________________________________________<br class="">OpenStack-dev mailing list<br class=""><a href="mailto:OpenStack-dev@lists.openstack.org" class="">OpenStack-dev@lists.openstack.org</a><br class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br class=""></div></blockquote></div><br class=""></div></body></html>