.n2.nabble.com/How-to-let-a-topic-receiver-know-that-the-related-topic-sender-has-gone-tp7621790p7621873.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr
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 cli
another way to let a
client
be somehow else notfied maybe by the using the broker's management interface
api
if a sender has gone? Assuming I could access that from a client.
Best regards
Jan
--
View this message in context:
http://qpid.2158936.n2.nabble.com/How-to-let-a-topic-receiver-kn
On 03/11/2015 11:10 AM, jml wrote:
Hi,
consider the following simple setup:
A topic exchange sender in c#, a c++ broker and a topic receiver in c#.
sender created with:
Sender _sender = session.CreateSender("test/AAA.B;{create:always, delete:
always, node:{type:topic}}");
receiver created with
find an
anwser yet.
Thx
jml
--
View this message in context:
http://qpid.2158936.n2.nabble.com/How-to-let-a-topic-receiver-know-that-the-related-topic-sender-has-gone-tp7621790.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
--
