[rabbitmq-discuss] How to attach C++ library?

Tue Jan 10 23:54:17 GMT 2012

Uday,

I will try to get you a bit of an example in the next day or so that will
hopefully illustrate how this might be done using the C API...

Regards,
Brett

On Fri, Jan 6, 2012 at 11:29 AM, Uday Subbarayan
<uday.subbarayan at yahoo.com>wrote:

> Thanks Brett for the pointer. I am aware of it.
>
> Our C++ server will act both as consumer of the message and also publisher
> of the message. The worker queue model will fit best. These servers are
> workers and will get the task via Rabbit MQ. After completing the task, it
> will post the status back to the queue.
>
> Best,
> -Uday.
>
>   ------------------------------
> *From:* Brett Cameron <brett.r.cameron at gmail.com>
> *To:* Uday Subbarayan <uday.subbarayan at yahoo.com>
> *Cc:* "rabbitmq-discuss at lists.rabbitmq.com" <
> rabbitmq-discuss at lists.rabbitmq.com>
> *Sent:* Wednesday, January 4, 2012 11:48 PM
> *Subject:* Re: [rabbitmq-discuss] How to attach C++ library?
>
> Uday,
>
> You should be able to do this using the C API (
> http://www.rabbitmq.com/c-client.html). What OS are you using? When you
> say that you want to convert the C++ code into a "socket based server",
> will it be acting purely as a consumer of messages (no response), or will
> it be operating in some sort of request/response (RPC) fashion?
>
> Brett
>
>
> On Thu, Jan 5, 2012 at 6:42 PM, Uday Subbarayan <uday.subbarayan at yahoo.com
> > wrote:
>
> Hi All,
>     Happy New Year.
>
> We have a C++ library which is currently used inside a product. We want to
> convert this library in to a socket based server and connect to Rabbit MQ
> so that it can consume & publish messages from the clients.
>
> Has any one done any similar work?
>
> Thanks,
> -Uday.
>
> _______________________________________________
> 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/20120111/0385664b/attachment.htm>