[rabbitmq-discuss] Fwd: .Net RabbitMQ.Client Issue: Deadlock on ConnectionShutdown

[Derek Greer]

>
> I propose that you look at the problem from another perspective. If a
> connection crashes then forget about that connection and all the
> channels contained in it. The library will clean them up. Return to the
> point of control where the connection was established and reconnect and
> re-establish brand new AMQP subscriptions.
>
>
I appreciate the suggestion and will give this some thought.


>
> The absence if renewable subscriptions may well be considered a flaw.
> Instead of trying to be all things to all people, the library instead
> offers the building blocks to build solutions that can hopefully suit
> every user. Signalling connection and channel lifetime events is an
> important component building block.
>
>
I'm not suggesting that the RabbitMQ client library provide renewable
subscriptions, but only that the building blocks provided not preclude
higher-level concepts such as this from being created by others.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120924/dae30e4d/attachment.htm>