Sure, that would be ideal, but that would require even more client side support, right?
<br/><br/><br/><br/>On Friday 22 November 2013 at 20:40, Alvaro Videla-2 [via RabbitMQ] wrote:
<br/><div class='shrinkable-quote'><br/>> What about a policy, which could be applied to users on a vhost, and
<br/>> that would tell home many channels a particular user can open? If the
<br/>> user is over the limit, then throw a channel exception?
<br/>>
<br/>> I'd guess then that users from a hosted RabbitMQ will know that they
<br/>> can open say 10 channels, or else get an exception.
<br/>>
<br/>> -Alvaro
<br/>>
<br/>> On Fri, Nov 22, 2013 at 2:06 PM, Michael Klishin <[hidden email] (/user/SendEmail.jtp?type=node&node=31584&i=0)> wrote:
<br/>>
<br/>> >
<br/>> > On 22 Nov 2013, at 15:07, carlhoerberg <[hidden email] (/user/SendEmail.jtp?type=node&node=31584&i=1)> wrote:
<br/>> >
<br/>> > > A configurable default channel_max would help a lot! the overwhelming majority of all uses-cases we see use only a handfull of channels anyway.
<br/>> >
<br/>> > More research suggests that many clients (including the most popular Java and Ruby ones) will need updating
<br/>> > to pick a lower configuration value than the server. So this is not something that can be fixed quickly.
<br/>> >
<br/>> > MK
<br/>> >
<br/>> > Software Engineer, Pivotal/RabbitMQ
<br/>> >
<br/>> >
<br/>> > _______________________________________________
<br/>> > rabbitmq-discuss mailing list
<br/>> > [hidden email] (/user/SendEmail.jtp?type=node&node=31584&i=2)
<br/>> > <a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss_______________________________________________" target="_top" rel="nofollow" link="external">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss_______________________________________________</a>
<br/>>
<br/>> rabbitmq-discuss mailing list
<br/>> [hidden email] (/user/SendEmail.jtp?type=node&node=31584&i=3)
<br/>> <a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_top" rel="nofollow" link="external">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br/>>
<br/>>
<br/>> If you reply to this email, your message will be added to the discussion below: <a href="http://rabbitmq.1065348.n5.nabble.com/channel-max-tp31572p31584.html" target="_top" rel="nofollow" link="external">http://rabbitmq.1065348.n5.nabble.com/channel-max-tp31572p31584.html</a>
<br/>> To unsubscribe from channel_max, click here (<a href="" target="_top" rel="nofollow" link="external">
<br/>> NAML (<a href="http://rabbitmq.1065348.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml" target="_top" rel="nofollow" link="external">http://rabbitmq.1065348.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml</a>)
</div><br/><br/><br/>
<br/><hr align="left" width="300" />
View this message in context: <a href="http://rabbitmq.1065348.n5.nabble.com/channel-max-tp31572p31597.html">Re: channel_max</a><br/>
Sent from the <a href="http://rabbitmq.1065348.n5.nabble.com/">RabbitMQ mailing list archive</a> at Nabble.com.<br/>