Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 74174 invoked from network); 8 Jun 2007 07:23:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 8 Jun 2007 07:23:21 -0000 Received: (qmail 77040 invoked by uid 500); 8 Jun 2007 07:23:25 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 76901 invoked by uid 500); 8 Jun 2007 07:23:25 -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 76892 invoked by uid 99); 8 Jun 2007 07:23:24 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Jun 2007 00:23:24 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.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; Fri, 08 Jun 2007 00:23:20 -0700 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1HwYoF-0000FC-Uz for dev@activemq.apache.org; Fri, 08 Jun 2007 00:22:59 -0700 Message-ID: <11021693.post@talk.nabble.com> Date: Fri, 8 Jun 2007 00:22:59 -0700 (PDT) From: Elber To: dev@activemq.apache.org Subject: Re: Routing information In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: shaheer@hotmail.fr References: <11008998.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org Thank you James. James.Strachan wrote: > > On 6/7/07, Elber wrote: >> >> Hello, >> >> I've faced the pb of "NC_Broker_Outbound already exists" and I want to >> know >> if there is a routing protocol which make brokers able to exchange >> informations about connected clients. >> So, a broker can have redundancy with clientId discovered and sent by a >> neighbor. > > Networks of brokers kinda do that kinda thing for store & forward. > Also Master/Slave for HA does similar things. > > Generally clientIDs are only required for durable topic subscriptions; > which are a bit sucky at times - whereas Virtual Topics are way > cooler... > > http://activemq.apache.org/virtual-destinations.html > > > -- > James > ------- > http://macstrac.blogspot.com/ > > -- View this message in context: http://www.nabble.com/Routing-information-tf3884166s2354.html#a11021693 Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.