<div class="gmail_quote">On Wed, Apr 14, 2010 at 11:13 AM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@rabbitmq.com">matthias@rabbitmq.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Dan Di Spaltro wrote:<br>
> On Wed, Apr 14, 2010 at 4:13 AM, Tony Garnock-Jones <<a href="mailto:tonyg@lshift.net">tonyg@lshift.net</a>> wrote:<br>
>> if only it were a per *queue* ttl, it'd be so much easier!<br>
> ttl's on a queue level would be very useful to us<br>
<br>
That's a really interesting idea, and it is a lot easier to implement<br>
than per-message TTLs.<br>
<br>
So here is a question to all RabbitMQ users who have been asking /<br>
secretly wishing for TTLs: Would per-queue TTLs, i.e. all messages<br>
getting the same TTL when they are enqueued, be good enough (or even<br>
preferable) for you? Or do you definitely need to be able to specify<br>
TTLs on per-message basis (and if so, what is the use case)?<br></blockquote><div><br>Per-queue would be far more useful IMO. Display the TTL's in rabbitmqctl list_queues and in the rabbitmq-status plugin and it'll be really easy to allow users to figure out why their messages are disappearing after $TTL seconds. It also makes the life of the administrator easier, since it would be visible without peeking at messages.<br>
<br>-Al<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Regards,<br>
<br>
Matthias.<br>
<br>
_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
</blockquote></div><br>