[rabbitmq-discuss] RabbitMQ .NET Client. Questions about QueueingBasicConsumer

Thu Jul 7 10:18:38 BST 2011

Thanks Emile, Simone.

I'll check out the channel QoS. The main reason I'm writing my own wrapper around QueueingBasicConsumer is because I'm multiplexing multiple subscriptions on a single consumer loop. I want the user of the API to simply call:

Subscribe<MyMessage>(MsgHandler);

And then have the API handle all the details :)

Mike

-----Original Message-----
From: Emile Joubert [mailto:emile at rabbitmq.com]
Sent: 07 July 2011 09:54
To: Mike Hadlow
Cc: Simone Busoli; rabbitmq-discuss at lists.rabbitmq.com
Subject: Re: [rabbitmq-discuss] RabbitMQ .NET Client. Questions about QueueingBasicConsumer

Hi Mike,

On 07/07/11 09:10, Simone Busoli wrote:
> Hi Mike, I'm quite new to RabbitMQ but I think there are at least a
> couple of things you can look into. One is QoS, which regulates how
> many messages a consumer is being pushed in advance, setting it to 1
> should

As Simone says, setting QoS on the channel will prevent a consumer from being flooded by messages.

You may also want to look at the Subscription class, another wrapper around QueueingBasicConsumer:

http://hg.rabbitmq.com/rabbitmq-dotnet-client/file/default/projects/client/RabbitMQ.Client/src/client/messagepatterns/Subscription.cs

-Emile

 15below Limited: Company registered in England and Wales No 3945289
Registered Office: Lyndean House, 43-46 Queens Road, Brighton BN1 3XB, United Kingdom

15below Australia Pty Limited: ABN 25 132 716 379
Level 50, 120 Collins Street, Melbourne, Victoria 3000, Australia

Please think about the environment before printing this email.

************************************************************************
This email and any attachments may be confidential and/or legally privileged and are solely for the use of the intended recipient.  If you have received this email in error please contact the sender.  Any views or opinions expressed within this e-mail are solely those of the sender, and do not necessarily represent those of 15below unless otherwise specifically stated.  Although 15below has taken every reasonable precaution to ensure that any attachment to this e-mail has been checked for viruses, it is strongly recommended that you carry out your own virus check before opening any attachment, as we cannot accept liability for any damage sustained as a result of software virus infection.