[rabbitmq-discuss] Synchronizing on Channel

[Aaron Westendorf]

If you're using transactions, that's not out of the question. If
you're using Python you can use or adapt haigha's ChannelPool and
frame queuing to see how that's done. In other languages or
situations, you could use a thread-safe queue and use the transaction
commit event to pull the next job off.

-Aaron

On Thu, Jun 30, 2011 at 9:53 AM, James Carr <james.r.carr at gmail.com> wrote:
> Hi All,
>
> We're currently integrating amqp-client into one of our legacy batch
> systems (to give you an idea, the project name has the word "threader"
> in it) and we've sadly discovered that reworking it to create a
> channel per thread will be extremely difficult. This has led me to
> wonder what the overhead costs are associated with sycnhronizing on
> channel? I don't want to do it, but it's one of those situations where
> reworking the legacy system might prove more expensive than the
> requirements need. :)
>
>
> Thanks,
> James
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>



-- 
Aaron Westendorf
Senior Software Engineer
Agora Games
359 Broadway
Troy, NY 12180
Phone: 518.268.1000
aaron at agoragames.com
www.agoragames.com