Show Table of Contents
Chapter 6. Advanced Queue Features
6.1. Browse-only Queues
Queues declared "browse-only" allow subscribers to access them and acquire their messages normally, but message acquisition transparently results only in a browse. The message will remain on the queue, and accessible to other subscribers.
Messages can only be removed from a browse-only queue by some non-acquisition mechanism: for example, when the message's TTL (time-to-live) duration expires.
The
spout and drain programs are part of the client libraries package and when installed can be found at:
/usr/share/doc/python-qpid-${version}/examples/api/
Here is an example of the creation and use of a browse-only queue by the spout and drain clients.
./spout \
-c 10 \
--broker "localhost:${PORT}" \
'q; {create: always, node:{type:queue , x-declare:{arguments:{"qpid.browse-only":1}}}}' \
"All work and no play makes Mick a dull boy."
./drain --broker 'localhost:${PORT}' 'q'
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.