On 12/09/14 04:50, Flavio Percoco wrote:
On 09/12/2014 12:14 AM, Zane Bitter wrote:
>However, Zaqar also supports the Pub-Sub model of messaging. I believe,
>but would like Flavio to confirm, that this is what is meant when the
>Zaqar team say that Zaqar is about messaging in general and not just
>queuing. That is to say, it is possible for multiple consumers to
>intentionally consume the same message, with each maintaining its own
>pointer in the queue. (Another way to think of this is that messages can
>be multicast to multiple virtual queues, with data de-duplication
>between them.) To a relative novice in the field like me, the difference
>between this and queuing sounds pretty academic :P. Call it what you
>will, it seems like a reasonable thing to implement to me.
Correct, this and other messaging patterns supported by Zaqar make it a
messaging service, which as Gordon mentioned in another email is just a
more generic term. Messages are the most important resource in Zaqar and
providing good, common and scalable patterns to access those messages is
what we strive for in Zaqar's API.
Thanks Flavio! I think we are more or less on the same page :)
Maybe you could clarify what the "other messaging patterns" are exactly,
since that seems to be one of the points of confusion/contention.
cheers,
Zane.
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
