<br><div class="gmail_quote">On Tue, Nov 2, 2010 at 8:41 AM, <span dir="ltr"><<a href="mailto:jiri@krutil.com">jiri@krutil.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
You can, but they'd have to set the x-message-ttl argument as part of the queue declaration.<br>
</blockquote>
<br></div>
Sure, but what if they don't want to cooperate?<br>
<br>
It seems to me that AMQP design in general assumes that peers always cooperate, which is a bit surprising for a protocol intended for communication across enterprises.<br></blockquote><div><br>Would it perhaps to plausible to implement some kind of AMQP policy
gateway between Rabbit and the external clients? This could enforce the
setting of various attributes on the declarations, and even allow for
far more advanced rules to be applied than Rabbit might want to support.<br><br>Paul.<br></div></div>