[rabbitmq-discuss] Scheduled Message Delivery

[Steve Powell]

Fascinating James,

I think the reason the queue stays around (even though you specify
auto-delete) is because auto-delete on queues is designed to be
triggered when the last consumer is cancelled. If there are never any
consumers for the queue this event never occurs and the queue stays
around. (If this wasn't the case, an auto-delete queue could disappear
as soon as it was created!). It's all in the spec  :-)

Steve Powell
steve at rabbitmq.com
[wrk: +44-2380-111-528] [mob: +44-7815-838-558]

On 30 Mar 2012, at 07:42, James Carr wrote:

> Hey All,
> 
> I thought I'd share a neat "trick" I came up with lately to "schedule"
> messages to be delivered at a specific duration. I had a lot of
> polling going on in my application for things like scheduling
> callbacks with leads and was getting sick of having to add even more
> interval based polling each time a new feature came along.
> 
> So here's an example of what I'm doing to schedule messages to be
> delivered at a time in the future:
> https://github.com/jamescarr/rabbitmq-scheduled-delivery. It makes
> interesting use of x-message-ttl and x-dead-letter-exchange. :)
> 
> Cheers,
> James
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss