On 01/10/2014 04:03 PM, Shearer, Davin wrote:
OK, I'm missing something. In the python code using proton, I have the
following lines:
reply_subscription = messenger.subscribe("amqp://%s/#" % host)
reply_address = reply_subscription.address
The reply address is being set to something like
ec940df5-4882-455a-bc14-49b2fb2c8ae1_receiver-xxx. I didn't think that an
AMQP 1.0 client could create nodes _that it named_ on the broker. AFAIK,
proton is all AMQP 1.0 all the time (and therefore should be vendor
agnostic), but yet using proton I was able to create a queue on my qpid
broker. So now the question is, who named it? The spec states that the
name of the dynamic queue is created by the broker (this is why the name
must not be set when using dynamic). In that python code snippet above, I
ask the broker for a dynamic node and I get the newly created node address
via the reply_subscription.address attribute, but the qpid broker did not
mark the queue as auto-del.
Many, many apologies! It appears this *has* been implemented in proton,
I was just unaware of it.
In the case above the dynamic flag is indeed set and the node name is
the one assigned by the broker. So that should work against other 1.0
brokers also.
Sorry for the misinformation folks! Messenger *can* create temporary queues.
(In my defense, the status of
https://issues.apache.org/jira/browse/PROTON-426 was misleading)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
