[rabbitmq-discuss] A new exchange type
0x6e6562 at gmail.com
Thu Jan 29 20:36:53 GMT 2009
On Wed, Jan 28, 2009 at 11:33 AM, Tony Garnock-Jones <tonyg at lshift.net> wrote:
> That's a great insight. We've been puzzling over "last-value caching"
> for a while now, and not made any great progress, largely I think
> because we'd concentrated on putting it in to the *queues* rather than
> the exchanges. Your observation that it's best placed in the *exchange*
> is, I think, critical. Great stuff!
Just a thought - what about implementing a queue that when the
consumer disconnects from it, it stays active but becomes bounded, so
that it only caches the last the n messages? Or maybe you could go one
step further and just put a user specified depth on the queue for it's
entire lifetime, so that you don't even need to bother with any
disconnection events? There are of course obvious disadvantages to
this approach, but it does solve your coherency issue.
More information about the rabbitmq-discuss