Davide
It´s very CPU and resource intensive. We use RedHat MRG (qpid 0.10) here,
and we ended-up creating specific receivers for each exchange type,
and using specific receiver for specific exchange in our middleware
abstraction code in this way...
qpid_context->m_direct_send
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
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
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?
Best,
Davide
-Original Message-
From: Andy Goldstein [mailto:agold...@redhat.com]
Sent: 26 January 201
The qpid::client API is an older API that is more closely tied to the
inner-workings of the AMQP 0-10 protocol.
The qpid::messaging API is newer and is generally recommended as the API to use
for new development effort. It is designed to abstract away from
protocol-specific details. This will
Hi,
Can anybody explain me what the difference between
qpid::messaging::Message and qpid::client::Message is?
I am trying to use VariantMap into the pub/sub example, but encode( ) is
only supported for qpid::messaging::Message.
Best,
Davide Anastasia
Analyst, Research & Development
Qual
Hi Steve,
I know and I can understand you are very busy since you are not posting much
these days. I just hope that you find sometime soon to answer these
questions.
Waiting...
Many thanks.
-Hamid
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Questions-regarding-Qpid-C-w
