<br><div class="gmail_quote">On Wed, Oct 28, 2009 at 3:48 PM, Garrett Smith <span dir="ltr"><<a href="mailto:g@rre.tt">g@rre.tt</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Yup, I'm familiar with those flags (and actually have read the spec, a<br>
few times even :)<br>
<br>
I need both non-exclusive/non-auto-delete so that the queue is<br>
preserved when either the creating connection or the last consumer<br>
goes away. Various agents come and go (restarting is one example, but<br>
there are other cases). Not to preach to the choir, but one of the<br>
benefits of async messaging is you can insulate from dropped<br>
connections.<br>
<br>
It sounds like I'm left with the option of running a cleanup/check<br>
process occasionally to ensure that we don't run into queues piling<br>
up. No other options, given exclusive=false and autodelete=false?<br>
<br>
I know that the expires/TTL is ignored in rabbit, and is perhaps not<br>
entirely fleshed out in the 0.8 spec, but it seems an important<br>
feature wrt resource resource management.<br>
<font color="#888888"><br>
</font></blockquote><div><br>Unless you've also got persitant messages, why not have auto-delete queues that every producer and consumer just declares up front? If no-one's around using that queue, it goes away, once someone needs it, the declare makes it appear.<br>
<br>Or am I missing something? <br></div></div><br>Robby<br><br>