Currently there is functionality built-in to client::Connection to check if
there's an amq.failover exchange, and if there is to subscribe for updates. This
is exposed to the user as client::Connection::getKnownBrokers() which returns
the updated set of brokers in the cluster.
I sorely regret building this in to client::Connection as has been nothing but
trouble. Currently it's causing sporadic memory leaks. It also does extra work
on _every_ Connection::open that is entirely useless if you're not talking to a
qpid C++ clustered broker.
I'd like to take it out and provide the functionality as a separate class that
users can employ if they actually want this functionality. Anyone know a reason
why I shouldn't do this?
Cheers,
Alan.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
