On 01/10/2014 01:34 PM, Shearer, Davin wrote:
I actually _prefer_ the C++ broker. I was using the java one for the web
management.
So to get this straight... proton sends '#' to the qpid broker, which in
turn generates a node name which it then sends back to the client via the
address attribute.
Not quite... The '#' is not part of the protocol between the client and
broker.
What actually happens is that proton (or qpid.messaging) sees the '#' in
the address and instead of sending a name across to the broker, sets the
"dynamic" flag in the attach frame, leaving the name blank. The broker
sees the dynamic flag, creates a temporary queue, and sends the name of
the queue back in the resulting attach frame.
The only thing at is missing is that the qpid broker
does not set auto-del on the newly created dynamic queue. If/When that's
fixed, I'm golden.
Thanks so much!
On Fri, Jan 10, 2014 at 11:51 AM, Gordon Sim <g...@redhat.com> wrote:
On 01/10/2014 02:26 PM, Shearer, Davin wrote:
I took some python code from Apache Dispatch Router and modified it to
work
with the qpid broker directly without using the dispatch router.
[...]
This is just using proton, which is great, but the problem is that the
dynamic queues have a permanent lifetime policy as demonstrated here:
Ok, this now is something that could be fixed in the broker. It could (and
arguably should) default to delete-on-close for dynamic nodes.
I've raised an issue to track that and will fix it before too long I hope:
https://issues.apache.org/jira/browse/QPID-5463
Your initial email suggested you were using the Qpid Java broker? That may
default as expected (Rob?).
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
