Re: limit policy on bound temporary queues

2012-12-18 Thread Jakub Scholz
Hi Lance, The address can be used in most of the new APIs - including C++ and Java. In C++ (the qpid.messaging API, not the deprecated qpid.client) you can pass this address as a string when creating the receiver using session.createReceiver(...). In Java, it is a bit more complicated, because you

Re: limit policy on bound temporary queues

2012-12-18 Thread Lance D.
Pavel, Thanks for making that more clear to me. I was aware that the _ queue was created as an auto-delete queue, but I wasn't aware that it was an auxiliary and exclusive queue. I'm going to look into what that implies in my application. But, yes, I'm trying to make that queue ("amq.fanout_18e

Re: limit policy on bound temporary queues

2012-12-18 Thread Lance D.
Thanks Jakub. Correct me if I'm wrong, but those commands to create the queue are the python commands, correct? What would that look like in c++? And I really like the ACL list idea. That will make it much easier to enforce proper client behavior. -Lance On Tue, Dec 18, 2012 at 3:01 AM, Jakub

Re: limit policy on bound temporary queues

2012-12-18 Thread Pavel Moravec
Hi Lance, let use in address string of the consumers just the exchange name, i.e.: "amq.fanout" qpid client will detect from an answer of qpid broker that "amq.fanout" is an existing exchange and it will create an auxiliary, auto-delete & exclusive queue named like "amq.fanout_18efcccb-3abb-4db

Re: limit policy on bound temporary queues

2012-12-18 Thread Jakub Scholz
Hi Lance, >From the client you can use address similar to this to create and temporary ring type queue: queue_1; { create: receiver, assert: never, node: { type: queue, x-declare: { auto-delete: true, exclusive: false, ar