[rabbitmq-discuss] Best way to ping server from client

James Gardner james.gardner at noaa.gov
Tue Dec 17 18:58:57 GMT 2013

Awesome Simon, very useful to know.
Can you also just confirm that adjusting QOS settings on a channel will 
have no effect on anything except message consumption, and no effect on 
using it for publishing or any other activity?
- James

On 12/17/2013 12:41 PM, Simon MacMullen wrote:
> On 17/12/2013 17:24, Alvaro Videla wrote:
>> On Tue, Dec 17, 2013 at 6:18 PM, James 
>> Gardner<james.gardner at noaa.gov>  wrote:
>>> >Great to get your reply, I didn't expect to hear from the 
>>> Creator;). Sorry
>>> >about the delay, I wanted to think further on this before responding.
>>> >The access_request idea was the type of answer I was looking for, 
>>> but alas:
>>> >http://www.rabbitmq.com/undeprecated.html
>>> >...so I can't base a solution on it.
>> I'm not sure IF we are ever going to remove the access class. Maybe
>> some other RabbitMQ dev can answer this question.
> Well, keeping compatibility with older clients tends to be more work 
> than we anticipate so these days we only tend to take things out if we 
> really need to, and I don't see a big need to ever take out 
> access.request.
> However, if you just want to issue an AMQP method that acts as a 
> no-op, it might be more future-proof to redeclare an already-existing 
> queue or exchange, or to reissue basic.qos. All of those tend to be 
> more or less a no-op if they don't change anything.
> Redeclaring a queue / exchange also has the advantage over basic.qos 
> and access.request that you can set no_wait = true and thus turn it 
> into an asynchronous method (i.e. you won't wait around for a 
> declare-ok).
> Cheers, Simon

More information about the rabbitmq-discuss mailing list