Mailing-List: contact users-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@qpid.apache.org
Received-SPF: pass (nike.apache.org: domain of kaner.mail@gmail.com designates
 209.85.210.170 as permitted sender)
MIME-Version: 1.0
Sender: kaner.mail@gmail.com
In-Reply-To: <5195EFE6.9080007@redhat.com>
References: 
 <CABop5eyAs8O2vEG3GY-4KSN04GLZNTgLQ=EJQ79+z63jkCWtsA@mail.gmail.com>
 <5195EFE6.9080007@redhat.com>
From: Christian Fromme <cfr@strace.org>
Date: Fri, 17 May 2013 14:21:07 +0200
Message-ID: 
 <CABop5exh6akS4xq53fa+2qzA5zWpj-qDAtopr_+beM6TEwdJOw@mail.gmail.com>
Subject: Re: Add route via C++ API?
To: users@qpid.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Hi,

On Fri, May 17, 2013 at 10:52 AM, Gordon Sim <gsim@redhat.com> wrote:

> Attached is a simple example showing what this would look like using the C++
> qpid::messaging API. It creates a link between two brokers and then
> established a flow of messages between the amq.fanout exchanges.
>
> Feel free to ask any questions as regrettably this is not terribly well
> documented.

Using the (newer) qpid::messaging API, I can't seem to find where to
add the routing-key for a bridge. I guess its somewhere through the
Variant::Map args? Are possible key/value pairs the broker understands
documented somewhere?

TIA again,
Christian

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org