[rabbitmq-discuss] immediate, mandatory flag with no consumers
Unni, Monish
munni at etrade.com
Fri May 4 20:43:05 BST 2012
Thanks for your replies Emile!
the only thing close to the c-client for basic.return i found this : https://groups.google.com/forum/#!msg/rabbitmq-discuss/fHL9tQHj4s0/FxCQxx4khKQJ
not sure if it does the same thing as java-api.
or if you could link me to github for this functionality.
kind regards,
-monish
On May 4, 2012, at 2:33 AM, Emile Joubert wrote:
> Hi,
>
> On 04/05/12 05:19, Unni, Monish wrote:
>> * is it okay to pair request-reply channels and use the same
>> connection to provide "maximum" concurrency?
>
> It is okay to send and receive messages on the same connection. Bear in
> mind that if the broker decides to block the connection then all
> channels in that connection will be affected. I'm not sure you will
> achieve higher concurrency this way.
>
>> * how can we get this feature working for "C" clients ( C- api ) ?
>
> Have you taken a look at the C client examples?
>
>> * and last : is my understanding right ( from observation ) that the
>> request channel and reply-channels have to share the same connection
>> for this feature to work?
>
> In general requests and their corresponding replies do not have to share
> a connection, but for basic.return to work the return handler must share
> a channel with the publisher.
>
> -Emile
>
More information about the rabbitmq-discuss
mailing list