Open Stack

2014-07-08 14:01 GMT-03:00 Gordon Sim <gsim at redhat.com>:

> On 07/08/2014 03:33 PM, Janczuk, Tomasz wrote:
>
>> What is the goal behind adding AMQP transport to Marconi? Would it make
>> sense to constrain Marconi to HTTP only instead? What is the value AMQP
>> adds that HTTP transport does not provide *in the context of Marconi*?
>>
>
> The HTTP interface is Marconi specific. AMQP is a standard protocol
> adopted by other messaging services, meaning an application written to use
> AMQP could be run against Marconi even if that was not the original (or
> only) target.
>
> I'm not arguing that Marconi should provide support for AMQP, but if it
> did I can see that being useful to some set of users.


Exactly that's what we are looking for with this addition.

Having support for more transport protocols would allow us to support a
broader set of use-cases. Also, Marconi could provide store-and-forward
capabilities to AMQP.

Does that make sense Tomasz?

Thanks for all your feedback Gordon, I really appreciate it.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140708/6aaa15be/attachment.html>