[rabbitmq-discuss] AMQP library APIs
Chris
stuff at moesel.net
Wed Aug 7 22:50:04 BST 2013
+1 for connection recovery and automatic fail-over in a cluster. In my
opinion, this should automagically connect/reconnect to the server,
redeclare and/or rebind any non-durable objects, and reconsume from the
queues. It should also reconsume if a master queue dies and a slave queue
is promoted.
I'm working on a project that uses amqp libraries in Java, C#, C++, and
node.js, and it's a pain to have to handle this ourselves in each (except
node-amqp, which mostly works for this). On the other hand, it's free, so
I try not to complain too much. ;-)
-Chris
On Wed, Aug 7, 2013 at 5:27 PM, Alan Antonuk <alan.antonuk at gmail.com> wrote:
>
> On Wed, Aug 7, 2013 at 1:11 PM, Michael Klishin <mklishin at gopivotal.com>wrote:
>
>>
>> amqp gem, Bunny serve as good examples of how it can be made much easier
>> for common cases. I hope to make HotBunnies and Langohr support the same
>> automatic recovery process fairly soon.
>>
>
> Interesting, whole connection recovery is something I haven't really
> considered. Any reason why individual channel recovery on error isn't
> implemented?
>
> I guess one thought I have had is to abstract away AMQP channels from the
> public API.
>
> _______________________________________________
> 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/20130807/fe93234c/attachment.htm>
More information about the rabbitmq-discuss
mailing list