Ben,<br><br>This is greatly welcome news! I look forward to the
implementation of this in the Erlang client, so that I can pause my
producers when I get the channel.flow command from the broker and avoid any possibility of exhausting Rabbit's memory. Any ETA?<br><br>Regards,<br>
Ed<br><br><div class="gmail_quote">On Sun, Nov 9, 2008 at 11:13 AM, Ben Hood <span dir="ltr"><<a href="mailto:0x6e6562@gmail.com">0x6e6562@gmail.com</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;">
Dear List,<br>
<br>
A few days ago I posted to this list to talk about scalable routing<br>
being one of the major pieces of work for the upcoming 1.5.0 release.<br>
<br>
Apart from being just just FYI about the release, it gives any body<br>
interested a chance to test it before we make the release.<br>
<br>
The same applies to the second major feature of this release -<br>
producer flow control.<br>
<br>
This is not only relevant for people who are maintaining client<br>
libraries - like me, who still has to handle it in the Erlang client<br>
:-( , but also for people who have applications that might send more<br>
messages than Rabbit can buffer in memory.<br>
<br>
The client side handling has been implemented in the Rabbit Java client.<br>
<br>
For those who are interested in the details, I've written this<br>
article: <a href="http://hopper.squarespace.com/blog/2008/11/9/flow-control-in-rabbitmq.html" target="_blank">http://hopper.squarespace.com/blog/2008/11/9/flow-control-in-rabbitmq.html</a><br>
<br>
HTH,<br>
<br>
Ben<br>
<br>
_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
<br>
</blockquote></div><br>