Nameko event max ttl?

Hi,

Is there a way to make an nameko event get deleted from rabbitmq if it has
been waiting to be processed for x seconds?

thanks

alternatively, how can we help nameko
support Time-To-Live and Expiration — RabbitMQ

···

On Friday, 27 October 2017 16:48:41 UTC+1, Richard wrote:

Hi,

Is there a way to make an nameko event get deleted from rabbitmq if it has
been waiting to be processed for x seconds?

thanks

Actually Nameko support for this landed in 2.7.0.

This is all you need to add per-message TTL for events:

class Service:
   name = "service"

   dispatch = EventDispatcher(expiration=300) # seconds

   ...

···

On Saturday, October 28, 2017 at 2:09:44 PM UTC+1, simon harrison wrote:

alternatively, how can we help nameko support
Time-To-Live and Expiration — RabbitMQ

On Friday, 27 October 2017 16:48:41 UTC+1, Richard wrote:

Hi,

Is there a way to make an nameko event get deleted from rabbitmq if it
has been waiting to be processed for x seconds?

thanks

Perfect, thanks

···

On Saturday, October 28, 2017 at 8:12:58 PM UTC+1, Matt Yule-Bennett wrote:

Actually Nameko support for this landed in 2.7.0.

This is all you need to add per-message TTL for events:

class Service:
   name = "service"

   dispatch = EventDispatcher(expiration=300) # seconds

   ...

On Saturday, October 28, 2017 at 2:09:44 PM UTC+1, simon harrison wrote:

alternatively, how can we help nameko support
Time-To-Live and Expiration — RabbitMQ

On Friday, 27 October 2017 16:48:41 UTC+1, Richard wrote:

Hi,

Is there a way to make an nameko event get deleted from rabbitmq if it
has been waiting to be processed for x seconds?

thanks