[rabbitmq-discuss] STOMP & expiration

[Steve Powell]

Toby,
See the post:
http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/2011-October/015635.html
and subsequent posts on that thread.

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

On 20 Oct 2011, at 01:10, Toby Corkindale wrote:

> On 22/08/11 19:13, Matthias Radestock wrote:
>> Lionel,
>> 
>> On 22/08/11 10:07, Lionel Cons wrote:
>>> It seems that RabbitMQ does not handle the "expires" STOMP header.
>>> 
>>> Although this is not in the STOMP spec, it's commonly used in
>>> JMS-compliant brokers to handle expiration.
>>> 
>>> Is there any plan to support message expiration via STOMP?
>> 
>> Is that header set on a per-message basis? If so then Rabbit won't
>> support that any time soon.
>> 
>> With AMQP we support a per-queue setting that controls message expiry.
>> See http://www.rabbitmq.com/extensions.html#queue-ttl.
> 
> 
> 
> I'm using the STOMP plugin for RabbitMQ, which is auto-vivifying the queues for me; is there an easy way to tell it to also pass the x-message-ttl header along?
> 
> (I'm happy to use the per-queue setting since the per-message stuff isn't implemented)
> 
> Cheers,
> Toby
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20111028/df9caa3b/attachment.htm>