The engine examples in python currently use a special send_msg() method
that is dynamically added to the sender objects created by the
'container'. I never really liked this mechanism, it was just a short
term workaround to get the simplicity I wanted to expose without
requiring changes to the
I use this field in my 'topologist' gadget that reads topology
information from a network of qdrouters.
I only have a connection to router A, but I am able to make topo
requests of the other routers (after I learn their names) by setting
the x-amqp-to field to a value like amqp:/_topo/0/QDR.B .
The current engine examples in python make use of an
OutgoingMessageHandler, that arranges for a callback to be made when the
sender has credit. At present that callback is called on_credit. However
I would like to change this to the slightly more general on_sendable.
By being more generally
I strongly agree with Keith that any change to the source tree should
happen (immediately) after (branching for) the next release. We can have
separate people managing the different components if we like, but I think
for this release we would be looking at a single release date and running
the
Great - thanks very much for the quick reply and explanation!
-Steve
-Original Message-
From: Rafael Schloming [mailto:r...@alum.mit.edu]
Sent: Monday, January 26, 2015 10:50 PM
To: users@qpid.apache.org
Subject: Re: Proton Java Messenger API questions
On Mon, Jan 26, 2015 at 5:38
+1. I like this change.
-Ted
On 01/27/2015 09:53 AM, Gordon Sim wrote:
The current engine examples in python make use of an
OutgoingMessageHandler, that arranges for a callback to be made when the
sender has credit. At present that callback is called on_credit. However
I would like to change
Based on what we've discussed so far, here's what I propose:
We prepare one more cross-component Qpid release, 0.32. This time, the
components share a version number and a source branch. Next time they
won't.
I'll manage the C++, Python, and related components. I will leave the Java
component
