Hi Hamza,
Actually I did exactly that (QMF using proton) as a demo for the proton
JavaScript binding so that should give you a few pointers. Take a look at:
proton/examples/javascript/messenger/qpid-config.js
Which is a pretty complete port of qpid-config written in pure
JavaScript using proton.
A few caveats.
1. the JavaScript binding uses a WebSocket transport so to talk to the
C++ broker I used a WebSocket to TCP socket proxy - that is probably no
odds to you as you want to use python, so what I've done is mainly
likely to be just a crib for what you want to do.
2. It uses the messenger API, the current feeling tends to be that the
reactor API is the way to go, unfortunately that's not something I'm
familiar with and I've been a bit distracted on other things so haven't
had time to look at that for JavaScript yet. Porting what I've done to
python's messenger API should work OK though it's just a question if
whether you want to use an API that isn't getting so much attention.
3. JavaScript is fundamentally asynchronous so I've had to put code in
place to correlate the QMF requests and responses, as it happens that
complication was one of the main reason I wanted to put together a demo.
With python messenger I *think* you could simplify things with
synchronous requests and responses.
4. I'm not overly familiar with python, but I did liberally crib the
python messenger binding for the JavaScript one, so I believe that you
just might get a fair bit of mileage if you look at qpid-config.js as a
starting point.
HTH,
Frase
On 22/01/16 18:07, Robbie Gemmell wrote:
On 21 January 2016 at 23:47, Hamza Sheikh <[email protected]> wrote:
I'm currently using qpid-python, qpid-tools, and qpid-qmf for
sending/receiving messages and to get info about/from the Qpid broker
(queues, stats, etc.).
Unfortunately, qpid-python is Python 2 only and does not support Python 3
(can't even pip install). I tried to port it to Python 3 but gave up because
(a) code quality is a complete mess, (b) messaging is not my passion, (c) I
did not have more time to spend on it.
My code depends on these three packages and I can't support Python 3 in my
code because of this limitation.
Can Proton replace qpid-python, qpid-tools, qpid-qmf for *both* my use
cases: (a) read/receive messages and (b) get info from the broker?
--
Hamza Sheikh
Twitter: @aikchar
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
I don't have much experience at all with the python bits components
but I believe the situation is such that the answer is generally yes,
you could use proton to send/receive messages and get info from the
broker, as the QMF tools are essentially sending/receiving
particularly formatted messages to the broker that you could similarly
produce/interpret yourself. The older components would have been using
AMQP 0-10, whereas with Proton you would be using AMQP 1.0, and so
there could be differences in specific approach due to that.
Robbie
---------------------------------------------------------------------
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]
