[rabbitmq-discuss] regarding SimpleAmqpClient

[Alan Antonuk]

Inlined:

On Thu, Mar 8, 2012 at 12:31 PM, Eric J. Holtman <eric at holtmans.com> wrote:

> On 3/8/2012 11:24 AM, Alan Antonuk wrote:
> > tedious at best).  That said if you're willing as a programmer to deal
> with
> > the library at a low level (mostly keeping track of frames that
> > are received from different amqp channels) there is nothing in the
> > rabbitmq-c library that prevents multiple consumers to be used.
> >
>
> Is SimpleAmqpClient doing that (keeping track of the frames)?
>
> Yes.


> Or maybe I'm not understanding the different levels... you're
> saying I can have two consumers on a channel, and that works,
> but what you cannot have is two channels using the same TCP
> connection?
>

Each SimpleAmqpClient AmqpClient::Channel object has exactly 1 TCP
connection.

Depending on what you're doing with the AmqpClient::Channel object it will
have 1 or more AMQP Channels open (this is not visible to you as a user of
the library).

Each AmqpClient::Channel object may have 1 or more consumers.

The limitation you're probably thinking about is that neither rabbitmq-c
nor SimpleAmqpClient is thread-safe.  If you want to use a
AmqpClient::Channel from different threads you need to synchronize its
usage, or just use a different AmqpClient::Channel instance from each
thread.

_______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>

-Alan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120308/353678f2/attachment.htm>