On 01/10/2014 02:03 PM, Davin Shearer wrote:
Sent from my iPhone
On Jan 10, 2014, at 13:49, Ted Ross <[email protected]> wrote:
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.
Right, but I'm pretty sure the magic '#' thing is a qpid::messaging thing, not
a proton thing and as such proton is actually sending '#' on the wire and qpid
messaging is doing the magic of creating the dynamic queue. The bit that's
missing is to set the lifetime policy to 'delete on close' which Gordon just
added into jira.
No. The '#' thing is done the same in proton-messenger as in
qpid::messaging. Both use the dynamic flag. Sending '#' on the wire is
not standard and the broker would not respond correctly to that.
It's important to note that this feature was recently introduced in
proton-messenger (as of 0.6).
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 <[email protected]> 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: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
