On 03/12/2015 11:16 AM, jml wrote:
one (but important) detail I missed to mention in the simple setup. It
is a one-to-many setup. A number of receivers consuming from the exchange.
As far as I understood a queue is for one-to-one communication.
I need to "broadcast" from a sender to multiple clients (receivers) and need
to let the clients know asap if a sender "has gone".
Ok, makes sense now. I can think of a few different options to consider:
(1) Use an LVQ or ring queue (to prevent unlimited growth) and have the
subscribers in browse mode. Delete the queue when the sender is
disconnected, which will cause the subscribers all to get an exception.
(2) Have the sender process set up a dummy queue, with a single message
in it and the alternate exchange set to be the exchange on which the
topic is based. This queue is deleted when the sender exits, at which
point the message on the dummy queue is routed through the exchange to
the subscribers. They then need to recognise it as a special indicator
that the sender has gone. (This is a bit like the mqtt last will and
testament feature).
(3) The subscribers could listen form management events about exchange
deletion to be notified when their topics exchange has been deleted
(The downside of this is that they need special permission and it is not
easy to give only fine grain control over management).
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
