On 08/23/2012 02:29 PM, mick wrote:
QPID-4241
Some messaging applications require browse-only functionality. Readers
of messages are never allowed to 'consume' the messages, because those
messages will always be relevant to newly arriving subscribers. ( Or at
least their loss of relevance is orthogonal to how many users have
already seen them. )
Browse-only functionality could be accomplished by constraining users,
through the ACL system, or by constraining queues at declaration time.
The two approaches are not equivalent, and both would probably be
worthwhile to implement at some point.
Agreed.
The ACL approach is preferable where you want a mixture of consumers and
browsers and want only certain users to be able to consume.
A queue option that makes the queue browse only is useful when you don't
want the receivers to have to care whether they are browsing or not,
i.e. where you want to control the distribution behaviour at the queue
rather than through each subscription request.
So I'd like to implement browse-only queues.
Sounds reasonable to me. It will strictly speaking be a 'violation' of
the AMQP 0-10 specification, but since it is explicitly configured that
is I think quite acceptable.
AMQP 1.0 provides better ways to manage the distribution centrally but
alerting consumers to the fact that they are not actually consuming in
case that is something they want to treat as an error. 9E.g. through the
first-acquirer header on delivered messages or the distribution mode on
the link source).
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
