Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: activemq-users@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: domain of sridharkomandur@gmail.com
 designates 66.249.92.192 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:references;
        b=nR1kai4o6VIT/psUb9NTzkxXkZOC4qgeY5KeBJGSKrzy1U1KVYTnjPJhzyaaxW8C5zAGEHIFbPeCv0jM7d54/OgJIF/D/kv5rHdqM69uVEqzDSEZYhCOrUgVEpAsz3iXfQOh6DTaDs+aQjFUaShN4Xle8Sr35og3Mio+JNU7f8k=
Message-ID: <ae7ffdb0602231408k360c297cvee87efdb6d6e8878@mail.gmail.com>
Date: Thu, 23 Feb 2006 14:08:49 -0800
From: "Sridhar Komandur" <anon2005@komandur.com>
Sender: sridharkomandur@gmail.com
To: user@activemq.codehaus.org
Subject: Re: [activemq-user] Network of Brokers ...
Cc: "ActiveMQ User" <activemq-users@geronimo.apache.org>
In-Reply-To: <BEFD19DC-EB58-4010-B864-853097051626@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_3415_26621135.1140732529513"
References: <ae7ffdb0602131515p280ddd26qff6c7ca51411f9f8@mail.gmail.com>
	 <BEFD19DC-EB58-4010-B864-853097051626@gmail.com>

------=_Part_3415_26621135.1140732529513
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Rob, thanks for your email.

Would you mind clarifying item 1 below, what if there are more than one pat=
h
between producer and a consumer for the given networkTTL ?

Will the consumer_broker receive as many messages as the number of paths ?
(I hope not). Could you please elaborate on the details of message routing
in this case ?

Thanks!
Regards
- Sridhar

On 2/19/06, Rob Davies <rajdavies@gmail.com> wrote:
>
>
> Networks are being updated currently for release 4.0
> Consumers are propagated around the network - but within constraints:
>
> 1. networkTTL - number of hops (brokers) that this information will
> pass through - networkTTL also applies to messages dispatched as well
> 2. exclusiveDestinations - can exclude destinations from network
> traffic (can use wild-cards etc)
> 3. inclusiveDestinations - can specify only destinations which are in
> the inclusive list to be propagated around the network
>
>
> I'll update the wiki with this information once we're satisfied its
> working.
>
> cheers,
>
> Rob
>
> On 13 Feb 2006, at 23:15, Sridhar Komandur wrote:
>
> > Hi,
> >
> > 1. Can anyone clarify how the routing info is shared within Network of
> > Brokers
> >      - is the producer/subscription info known to all the brokers
> > in the
> > network ? As I understand,
> >     4.0 follows demand-forwarding for the actual message flow.
> >
> > 2. Has anyone /deployed/thought of/ an architecture where multiple
> > "Network
> > of Brokers" clusters would be deployed ?
> >      (not unlike ISP domains, within the same enterprise - for
> > capacity or
> > ownership reasons).
> >     I was wondering how  "routes" can be selectively disseminated
> > between
> > the clusters.
> >
> >
> > Thanks for any insights into the above.
> >
> > Thanks
> > Regards
> > - Sridhar Komandur
>
>

------=_Part_3415_26621135.1140732529513--