<div>Regarding the caveats and triggering expiry only on a message at the head of the queue, are there plans to support message expiration independent of position in queue?</div><div><br></div><div>Just to clarify on the current 3.0 implementation, if I understand this correctly, this means that if I have two unconsumed messages (e.g. the queue's consumer has disappeared for several minutes) where the first message has no TTL and the second has a 5 second TTL, this 5 second TTL message will not be dead lettered until the non-TTL message is consumed?</div>
<div><br></div><div>Thanks,</div><div><br></div><div>-Randall<br><br><div class="gmail_quote">On Wed, Nov 28, 2012 at 2:54 AM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@rabbitmq.com" target="_blank">matthias@rabbitmq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 28/11/12 07:21, Michael Klishin wrote:<br>
�> 2012/11/28 Tanya Skuridina <<a href="mailto:tantigrenok@gmail.com" target="_blank">tantigrenok@gmail.com</a><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<mailto:<a href="mailto:tantigrenok@gmail.com" target="_blank">tantigrenok@gmail.com</a>><u></u>><div class="im"><br>
<br>
� � I have an interesting question about delayed message consuming - Is<br>
� � it possible to publish a message to be consumed at a later date (set<br>
� � somewehere in params)?<br>
<br>
� � Anybody else encountered this problem?<br>
<br>
� � I found this link<br></div>
� � <a href="http://blog.james-carr.org/__2012/03/30/rabbitmq-sending-a-__message-to-be-consumed-later/" target="_blank">http://blog.james-carr.org/__<u></u>2012/03/30/rabbitmq-sending-a-<u></u>__message-to-be-consumed-<u></u>later/</a><div class="im">
<br>
� � <<a href="http://blog.james-carr.org/2012/03/30/rabbitmq-sending-a-message-to-be-consumed-later/" target="_blank">http://blog.james-carr.org/<u></u>2012/03/30/rabbitmq-sending-a-<u></u>message-to-be-consumed-later/</a>><br>
<br>
<br>
Tanya,<br>
<br>
RabbitMQ does not support scheduled message delivery.<br>
</div></blockquote>
<br>
Well, it does, with the trick above, i.e. using a combination of message expiry (per-queue message ttl prior to 3.0, and that or per-message ttl in 3.0, though note the caveats <a href="http://www.rabbitmq.com/ttl.html#per-message-ttl-caveats" target="_blank">http://www.rabbitmq.com/ttl.<u></u>html#per-message-ttl-caveats</a>) and dead lettering.<br>
<br>
Regards,<br>
<br>
Matthias.<div class="HOEnZb"><div class="h5"><br>
<br>
______________________________<u></u>_________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.<u></u>rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/<u></u>cgi-bin/mailman/listinfo/<u></u>rabbitmq-discuss</a><br>
</div></div></blockquote></div><br></div>