[rabbitmq-discuss] Client implementation in C++

Alan Antonuk alan.antonuk at gmail.com
Mon Mar 11 22:51:31 GMT 2013

Interesting concept.

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 (


On Thu, Mar 7, 2013 at 11:39 AM, Alterman, Eugene <
Eugene.Alterman at infogroup.com> wrote:

>  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.
> Is there any interest in a library based on such an approach?
> A very preliminary sources with a consumer example is here:
> https://github.com/eugene-a/amqcpp.
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130311/0efa2885/attachment.htm>

More information about the rabbitmq-discuss mailing list