Re: Reusing messaging::Sender vs creating every time

2013-11-29 Thread Gordon Sim
On 11/29/2013 02:47 PM, Toralf Lund wrote: On 29/11/13 14:00, Gordon Sim wrote: When creating the receiver for responses, use an address like e.g. "amq.direct/#; {node:{type:topic}}", That simple, eh? I somehow imagined that I had to explicitly set up bindings via e.g. x-bindings, and also care

Re: Reusing messaging::Sender vs creating every time

2013-11-29 Thread Toralf Lund
On 29/11/13 14:00, Gordon Sim wrote: On 11/29/2013 11:17 AM, Toralf Lund wrote: On 29/11/13 11:19, Gordon Sim wrote: On 11/29/2013 09:08 AM, Toralf Lund wrote: One option to reduce the number of distinct senders, and therefore benefit more from caching, is to use a single a sender per exchange

Re: Reusing messaging::Sender vs creating every time

2013-11-29 Thread Gordon Sim
On 11/29/2013 11:17 AM, Toralf Lund wrote: On 29/11/13 11:19, Gordon Sim wrote: On 11/29/2013 09:08 AM, Toralf Lund wrote: One option to reduce the number of distinct senders, and therefore benefit more from caching, is to use a single a sender per exchange (this is with AMQP 0-10) and just set

Re: Reusing messaging::Sender vs creating every time

2013-11-29 Thread Toralf Lund
On 29/11/13 12:48, Bruno Matos wrote: On 11/29/2013 11:17 AM, Toralf Lund wrote: On 29/11/13 11:19, Gordon Sim wrote: On 11/29/2013 09:08 AM, Toralf Lund wrote: Hi, Just wondering, what gain is there in reusing Sender objects for the C++ Messaging API? I mean, over doing something like qpi

Re: Reusing messaging::Sender vs creating every time

2013-11-29 Thread Toralf Lund
On 29/11/13 12:48, Bruno Matos wrote: On 11/29/2013 11:17 AM, Toralf Lund wrote: On 29/11/13 11:19, Gordon Sim wrote: On 11/29/2013 09:08 AM, Toralf Lund wrote: Hi, Just wondering, what gain is there in reusing Sender objects for the C++ Messaging API? I mean, over doing something like qpi

Re: Reusing messaging::Sender vs creating every time

2013-11-29 Thread Bruno Matos
On 11/29/2013 11:17 AM, Toralf Lund wrote: On 29/11/13 11:19, Gordon Sim wrote: On 11/29/2013 09:08 AM, Toralf Lund wrote: Hi, Just wondering, what gain is there in reusing Sender objects for the C++ Messaging API? I mean, over doing something like qpid::messaging::Sender sender=session.cre

Re: Dynamic routes

2013-11-29 Thread Bruno Matos
On 11/28/2013 06:29 PM, Gordon Sim wrote: On 11/28/2013 05:40 PM, Bruno Matos wrote: Hello, I'm using dynamic routes between two federated Brokers and I'm having some problems. Here is the scenario: I have one client connected to one Broker (A), which sends a request to a service witch is conne

Re: Reusing messaging::Sender vs creating every time

2013-11-29 Thread Toralf Lund
On 29/11/13 11:19, Gordon Sim wrote: On 11/29/2013 09:08 AM, Toralf Lund wrote: Hi, Just wondering, what gain is there in reusing Sender objects for the C++ Messaging API? I mean, over doing something like qpid::messaging::Sender sender=session.createSender(address); sender.send(message); sen

Re: Reusing messaging::Sender vs creating every time

2013-11-29 Thread Gordon Sim
On 11/29/2013 09:08 AM, Toralf Lund wrote: Hi, Just wondering, what gain is there in reusing Sender objects for the C++ Messaging API? I mean, over doing something like qpid::messaging::Sender sender=session.createSender(address); sender.send(message); sender.close(); every time? The bigges

Reusing messaging::Sender vs creating every time

2013-11-29 Thread Toralf Lund
Hi, Just wondering, what gain is there in reusing Sender objects for the C++ Messaging API? I mean, over doing something like qpid::messaging::Sender sender=session.createSender(address); sender.send(message); sender.close(); every time? I'm thinking about this in conjunction with a request