On 06/02/14 19:07, CLIVE wrote:
Hi,
[snip]
The first use case requires the dynamic creation of Receivers, but
before creating a new receiver, I would like to know if I already have
a receiver that would match the required binding. This is not possible
at the moment because the binding
On Tue, Feb 4, 2014 at 4:23 PM, Steve Huston shus...@riverace.com wrote:
On the Contributors page, in thanks section, it would be good to mention
Coverity for allowing us use of Coverity Scan to do static analysis.
You're right, of course! I've added them to the companies section of
the
On Wed, Feb 5, 2014 at 10:58 AM, Gordon Sim g...@redhat.com wrote:
On 02/05/2014 03:51 PM, Alan Conway wrote:
I never noticed developer central before - very handy set of
shortcuts!
Indeed! I would think this was useful to users and developers alike. Could
we make it more prominent somehow?
Great! Thanks!
-Steve
On Feb 7, 2014, at 7:38 AM, Justin Ross jr...@apache.org wrote:
On Tue, Feb 4, 2014 at 4:23 PM, Steve Huston shus...@riverace.com wrote:
On the Contributors page, in thanks section, it would be good to mention
Coverity for allowing us use of Coverity Scan to do
I'm writing a how-to document for the Apache.NMS.AMQP Provider (a .NET
subsystem to provide AMQP support to http://activemq.apache.org/nms/). I'm
looking for a pointer to a description of the C++ Messaging API connection URL.
The C++ connection options are easy enough to find:
On 02/07/2014 03:00 PM, Chuck Rolke wrote:
I'm writing a how-to document for the Apache.NMS.AMQP Provider (a .NET
subsystem to provide AMQP support to http://activemq.apache.org/nms/). I'm
looking for a pointer to a description of the C++ Messaging API connection URL.
The C++ connection
Hi Chuck,
I think that the
http://qpid.apache.org/releases/qpid-0.24/programming/book/connection-options.html
book is indeed where most people would tend to look, but it's not quite
complete
The qpid::messaging API doxygen docs
On 02/07/2014 03:43 PM, Fraser Adams wrote:
I do rather wonder that for AMQP 1.0 if the URL could be improved to
accept something like:
amqp://[user][:password@][proto:]host[:port]
I think for consistency it would be better to drop the proto part and
use amqp/amqps as the scheme there.
On 07/02/14 16:00, Gordon Sim wrote:
On 02/07/2014 03:43 PM, Fraser Adams wrote:
I do rather wonder that for AMQP 1.0 if the URL could be improved to
accept something like:
amqp://[user][:password@][proto:]host[:port]
I think for consistency it would be better to drop the proto part
and use
From: Fraser Adams fraser.ad...@blueyonder.co.uk
Sent: Friday, February 7, 2014 10:43:06 AM
Note that for qpid::messaging this stuff is all in the connection
options, the actual URL is usually just set as just a basic
host:port, though actually I *think* that it is an AMQP 0.10 URL and
you
On Fri, 2014-02-07 at 16:48 +, Fraser Adams wrote:
... TBH I mainly mentioned it because when I was going
through my exercise of trying out various AMQP 1.0 subscribers I was
starting to find the:
--connection-options {protocol:amqp1.0}
A little bit less aesthetically pleasing than
11 matches
Mail list logo
