Whooops, spoke too soon - it looks like this is explicitly supported in 0.14.0.
Sorry for the noise.
Jeff
From: Jeff Donner [jdon...@morphodetection.com]
Sent: Tuesday, September 06, 2016 4:13 PM
To: users@qpid.apache.org
Subject: Any way to do consumer f
Hi,
Is there any way to do consumer-side flow control from Proton C++? I'm
currently using 0.12.1, but I don't see anything different from what I did
below even in 0.14.0.
I added the following lines to the example simple_recv.cpp 's on_message()
handler,
std::cout << "received; c
The Apache Qpid community is pleased to announce the immediate
availability of Apache Qpid C++ 1.35.0.
Apache Qpid (http://qpid.apache.org) is a cross-platform enterprise
messaging solution which implements the Advanced Message Queuing Protocol
(AMQP, http://www.amqp.org). It provides message brok
+1
* Reviewed the source and binary distribution files
* Checked license and notice files
* Validated Signatures and Checksums
* Built from the source distributions and ran the tests.
* Tested an ActiveMQ 5.x broker using the staged artifacts
* Ran the example against an existing ActiveMQ 5.x bro
Hi,
I have implemented an AMQP 1.0 server on top of vertx-proton (using
proton-j under the hood). When I connect to the server, I get the
impression that the server will only accept and establish a single
connection per client (identified by IP address/port).
Is that right, and is this configurab
On Sat, 2016-09-03 at 09:26 +0200, Volker Diels-Grabsch wrote:
> Hi Gordon, Ken,
>
> Thanks for your useful explainations. Neither of them solved my
> problem fully, but the combination did. :-)
Here is a relatively simple procedure for building a python package
like you describe from the source
On 05/09/16 16:47, Robbie Gemmell wrote:
Hi folks,
I have put together a spin for a 0.11.0 Qpid JMS client release, please
test it and vote accordingly.
+1 (verified signature, compiled and ran tests, ran helloworld example
against both brokers, the router and the proton python broker.py exam
+1 ... I took the staged artifacts and run my tests against different
versions of Qpid C++ broker (0.34, 1.35 and master) and Red Hat MRG-M 3.2.
All seems to work OK.
On Mon, Sep 5, 2016 at 5:47 PM, Robbie Gemmell
wrote:
> Hi folks,
>
> I have put together a spin for a 0.11.0 Qpid JMS client rel
