OK - ensuring all bound queues receive messages in the same order is a sensible policy option - though adding a sequence number seems slightly orthogonal to that. As you suggest the other alternative there is for a single queue implementation of "topic" - I actually have one of those for the Java Broker that I did as part of the AMQP 1.0 work.
-- Rob On 22 August 2012 16:30, Gordon Sim <g...@redhat.com> wrote: > On 08/22/2012 03:15 PM, Rob Godfrey wrote: >> >> I looked at this >> briefly before but couldn't really understand a use case where this >> feature would be useful. >> >> Are you looking for the broker to identify a total ordering over all >> messages going through an exchange? Do you need an incrementing >> integer? > > > The feature on the c++ broker was for a totally ordered sequence of all > messages through the exchange. The pre-1.0 AMQP model is not ideal for > pub-sub where you want all subscribers to receive events in the same order. > That extension to the exchange was a way of working around it where > absolutely needed. > > I think actually a modified browsable queue would be a better approach, > where messages were deleted after being seen by all browsers. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > For additional commands, e-mail: users-h...@qpid.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
