[rabbitmq-discuss] Message timeouts

Alex Grönholm alex.gronholm at nextday.fi
Wed May 2 08:20:20 BST 2012

02.05.2012 08:26, Matthias Radestock kirjoitti:
> Alex,
> On 01/05/12 23:38, Alex Grönholm wrote:
>> 30.04.2012 19:59, Matthias Radestock kirjoitti:
>>> Right. Ideally you'd need a way to specify a dead-letter destination
>>> *per message*. However, working with what is possible today, instead
>>> you could just have a single "dead request" queue to which all expired
>>> requests get routed. And then have a small app simply consuming
>>> messages from that queue and replying to them with some sort of error
>>> indication.
>> That did occur to me, but if I was able to launch an "answering machine"
>> app, why not the real one too while I'm at it?
>> Thanks for the answer, but is there any hope for a real solution? Could
>> this be cleanly done with a plugin?
> Yep. It could be done cleanly with a plugin that employs the Erlang 
> client in 'direct' mode to implement said "answering machine" app.
> Of course if you take that approach to the extreme then you'd write 
> your *entire* app as a plugin ;)
> Matthias.
No thanks, I've looked into the Erlang language and while I like many of 
the ideas and patterns it employs, Python's syntax still wins big time 
for its power and efficiency.

More information about the rabbitmq-discuss mailing list