Ok, got it.

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.

Thanks

Renat Akhmerov
@ Mirantis Inc.



> On 09 Dec 2014, at 08:25, W Chan <m4d.co...@gmail.com> wrote:
> 
> Renat,
> 
> On sending events to an "exchange", I mean an exchange on the transport (i.e. 
> rabbitMQ exchange https://www.rabbitmq.com/tutorials/amqp-concepts.html 
> <https://www.rabbitmq.com/tutorials/amqp-concepts.html>).  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.
> 
> Winson
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to