qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davide Anastasia" <Davide.Anasta...@qualitycapital.com>
Subject RE: Differences between Message classes in Qpid C++ API
Date Thu, 26 Jan 2012 17:50:40 GMT
Thanks Gordon,	
I end up setting the routing key in the createSender( ) and
createReceiver( ) function: is this a common solution? How expensive is
to create a new Sender for every new message?

Last question: should I be using Runnable and Thread to implement what
in the old API was performed by the MessageListener? Is there anything
similar to the class SubscriptionManager in the new API?

Best regards,
Davide 

-----Original Message-----
From: Gordon Sim [mailto:gsim@redhat.com] 
Sent: 26 January 2012 14:08
To: users@qpid.apache.org
Subject: Re: Differences between Message classes in Qpid C++ API

On 01/26/2012 02:06 PM, Davide Anastasia wrote:
> Hi Andy,
> Thanks for the quick reply: it did help. In fact I made my code 
> compile, but unfortunately I can't find a way to set the routing_key 
> using the new API. What's the quickest way?

Set the subject. Provided you send to a named exchange, that will then
be taken as the routing key to use. You can also specify the default
subject for the sender in the address e.g. my-exchange/my-key.

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org


Mime
View raw message