<div dir="ltr">Interesting concept. <div><br></div><div>Care to give a few words (or examples) on the benefits of using the design patterns you choose to use? E.g., What advantages or situations might this API design be more suitable than say SimpleAmqpClient (<a href="https://github.com/alanxz/SimpleAmqpClient">https://github.com/alanxz/SimpleAmqpClient</a>).<div>
<br></div><div style>-Alan</div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Mar 7, 2013 at 11:39 AM, Alterman, Eugene <span dir="ltr"><<a href="mailto:Eugene.Alterman@infogroup.com" target="_blank">Eugene.Alterman@infogroup.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div style="direction:ltr;font-size:10pt;font-family:Tahoma">I started writing a rabbitmq C++ client library. It is of course layered on top of rabbitmq-c and utilizes boost meta state machine to process incoming protocol frames. Processing
of each incoming frame returns an instance of a boost variant. The static visitor is applied to each result. When a message is delivered, the instance of the visitor will store all the information.<br>
<br>
Is there any interest in a library based on such an approach?<br>
<br>
A very preliminary sources with a consumer example is here: <a href="https://github.com/eugene-a/amqcpp" target="_blank">https://github.com/eugene-a/amqcpp</a>.<br>
</div>
</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></div>