I don't know AMQP very well. At the protocol level, are Exchanges, Queues, etc things? Are fanout, durability, and other things required or optional to be implemented?
Thanks, Kevin ________________________________________ From: Gordon Sim [g...@redhat.com] Sent: Thursday, May 28, 2015 10:05 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Zaqar][all] Zaqar will stay... Lots of work ahead On 05/28/2015 05:14 PM, Fox, Kevin M wrote: > Thats like saying you should implement a sql engine inside of > Berkeley DB since so many folks like sql... Not a good fit. If you > want AMQP, get an AMQP server. Zaqar's intentionally lighter weight > then that. Hardly any OpenStack services use but a fraction of AMQP > though, so getting oslo.messaging to support that simple subset of > AMQP on top of Zaqar is much more reasonable then getting Zaqar to > support all of AMQP. AMQP 1.0 is just a protocol for asynchronously transferring messages between processes. Supporting it doesn't require that zaqar provide any functionality that it doesn't want to. It is simply another protocol for accessing exactly the same service. __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
