<blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">However, we're more likely to go in the direction of having things like HA-ness defined outside of the AMQP arguments mechanism altogether in future</blockquote>
<div> </div><blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">The application should not have to know that its queues are HA or its exchanges are federated; that's a matter for the broker administrator</blockquote>
<div class="gmail_extra"><br></div><div class="gmail_extra">Great to hear that you've got that in mind, Simon! It would improve things immeasurably for both application code, broker management, and coincidentally is my biggest gripe with the current state of RabbitMQ HA. Would love to see work in that direction sometime in the future.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">- Brendan<br><br><div class="gmail_quote">On Fri, Apr 20, 2012 at 6:56 PM, Simon MacMullen <span dir="ltr"><<a href="mailto:simon@rabbitmq.com" target="_blank">simon@rabbitmq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">We're aware that the current situation with HA policies is inconvenient; it was the simplest thing that could possibly work.<br>
<br>
However, we're more likely to go in the direction of having things like HA-ness defined outside of the AMQP arguments mechanism altogether in future. Really arguments should be for things that application authors care about; it's a contract with the application that these should not change. The application should not have to know that its queues are HA or its exchanges are federated; that's a matter for the broker administrator.<br>
<br>
Cheers, Simon<div><div class="h5"><br>
<br>
On 20/04/12 17:51, Elias Levy wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
Are there any plans to allow the modification of queue and exchange<br>
attributes, say via the REST API?<br>
<br>
At the moment if one must redefine the attributes of a queue or<br>
exchange, you must destroy the queue or exchange and recreate it. That<br>
is rather disruptive in a production environment. If means that<br>
bindings are destroyed and must be recreated, that consumers must<br>
restart their subscriptions, etc.<br>
<br>
There are many scenarios where one would want to redefine the<br>
attributes. Either an error crept in during initial set up, or say, a<br>
node has gone down and you want to redefine a HA queue by removing the<br>
dead node from its config and adding a new node.<br>
<br>
Thoughts?<br>
<br>
Elias Levy<br>
<br>
<br>
<br></div></div>
______________________________<u></u>_________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.<u></u>rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/<u></u>cgi-bin/mailman/listinfo/<u></u>rabbitmq-discuss</a><span class="HOEnZb"><font color="#888888"><br>
</font></span></blockquote><span class="HOEnZb"><font color="#888888">
<br>
<br>
-- <br>
Simon MacMullen<br>
RabbitMQ, VMware<br>
______________________________<u></u>_________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.<u></u>rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/<u></u>cgi-bin/mailman/listinfo/<u></u>rabbitmq-discuss</a><br>
</font></span></blockquote></div><br></div>