On Wed, Nov 25, 2009 at 3:05 PM, Carl Trieloff <[email protected]>wrote:
> Cullen Davis wrote: > >> Leticia, >> >> We are using the federation feature to provide our application with >> "exchange extensibility" (my term). Instead of federating for capacity >> scaling, we our federating for content scaling. Our application is >> completely self-sufficient and deployed to multiple sites. We do not have >> any transactional constraints on our solution but there are times when two >> application installations will need to share information (and act >> independently on the messages). Dynamic Exchange Federation gives us the >> ability to to join the two broker's at the exchange and propagate message >> traffic. The fact that the federation can be directional gives us even more >> flexibility. This provides us for the ability to grow or shrink message >> visibility in a way that directly maps to the customers data domains. >> >> >> > > Cullen > > This is a nice use case, if you want to write it, we could add it to the > wiki as I think it would be helpful to many users. > > Carl. > > I think that this sounds really nice too. > I would like that the sw that we are developing can manage with two or more federated qpid brokers. In order to obtain this, we need more information about how to communicate to the brokers how to share the state (and create the link or bridge) and how to solve the fault tolerance issue. Is there any manner to configure using a configuration file or can we do it dynamically ? If you could give me any kind of information about this topic it will be very useful. Thanks --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] > >
