<div>Hi - current maintainer of the rabbitmq-c library here;</div><div><br></div><div>I don't know the entire history behind the rabbitmq-c library, however as I understand the label 'experimental' has a lot to do with the fact the library was not given the same amount of attention as the other official Java, .NET and Erlang clients, and thus was not promised the same amount of support the other clients were given.</div>
<div><br></div><div>I would give the library the label "beta" currently.</div><div><br></div><div>The library does support the current feature set of the latest RabbitMQ broker (v2.8.1)</div><div>The library has been used in limited amount of production scenarios (that I know about) and been shown to be stable in the cases I know about</div>
<div>The API definitely needs some love, especially in the area of consuming messaging and dealing with asynchronous events</div><div>Currently the library lacks good documentation and packaging</div><div><br></div><div>-Alan</div>
<div><br></div><div class="gmail_quote">On Mon, Apr 2, 2012 at 12:13 PM, Brendan Hay <span dir="ltr"><<a href="mailto:brendan@soundcloud.com">brendan@soundcloud.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Yo,<div><br></div><div>Is the rabbitmq-c library still considered experimental, if so, for what reasons? (lack of functionality, lack of love, etc.)</div><div><br></div><div>Thanks,</div><div>Brendan</div>
<br>_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
<br></blockquote></div><br>