Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 54181 invoked from network); 10 Dec 2008 21:57:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Dec 2008 21:57:10 -0000 Received: (qmail 90872 invoked by uid 500); 10 Dec 2008 21:57:22 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 90684 invoked by uid 500); 10 Dec 2008 21:57:22 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 90673 invoked by uid 99); 10 Dec 2008 21:57:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Dec 2008 13:57:22 -0800 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Dec 2008 21:57:07 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1LAX30-0002KP-PR for dev@activemq.apache.org; Wed, 10 Dec 2008 13:56:46 -0800 Message-ID: <20944957.post@talk.nabble.com> Date: Wed, 10 Dec 2008 13:56:46 -0800 (PST) From: daven1986 To: dev@activemq.apache.org Subject: Networked brokers - a few questions MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: daven.gahir@gmail.com X-Virus-Checked: Checked by ClamAV on apache.org Hi, I have a few questions about message routing and broker networks. The layout I am talking about is one like this: broker A ---> producer, producer, consumer | | broker B ---> producer, consumer | | broker C ---> producer, consumer, consumer I want to optimise the performance when a consumer connected to broker A wants to consume messages of a certain topic, and a producer connected to broker C is producing these messages. I was thinking about extending the DemandForwardingBridge class and overriding any necessary methods. I want to be able to maintain a list of remote brokers and the topics the consumers of each broker are subscribed to, at each broker. I also want to be able to hold a list of routes to each broker. These will be called upon to decide where to send each message. My questions are: 1) How does ActiveMQ currently handle such a situation? 2) Would my method be the correct way of going about this? 3) As far as I understand it, when a connection is made broker to broker the "start" method of the network bridge is called, and then to send a message it calls the "oneway" method of the transport on the required connection. Is this correct? 4) How would I configure the brokers to use my new network bridge when I implement it? Many thanks Daven -- View this message in context: http://www.nabble.com/Networked-brokers---a-few-questions-tp20944957p20944957.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.