Mailing-List: contact camel-dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: camel-dev@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of ramon.buckland@gmail.com
 designates 64.233.170.186 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:in-reply-to:mime-version
         :content-type:references:x-google-sender-auth;
        b=EBCXlWHddhp7kq7z46Z1f6wkLJ1gcgflj4wqvpJMFZTe6fMapEkuYkOH37LUg/hBwe
         7d7fqA49jGirZQf+UnmD2QmRL7gkcAw/nWv9zRG7bLmN80hjLvFuHLkB+PH7sJM923zz
         diQAQxyAatgRTOQy3Iei0A4YQRp4mJyLPBSdA=
Message-ID: <509899e80812110536o45e293eaocacdbf8aa9cc6fb1@mail.gmail.com>
Date: Fri, 12 Dec 2008 00:36:56 +1100
From: "Ramon Buckland" <ramon@thebuckland.com>
Sender: ramon.buckland@gmail.com
To: camel-dev@activemq.apache.org
Subject: Re: [jira] Created: (CAMEL-1183) rename multicast -> wireTap in the
 Java DSL and XML config?
In-Reply-To: <ec6e67fd0812110519m5caed8f9h4a5ea6990ce16a89@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_7434_3924680.1229002616238"
References: <662063655.1228999205512.JavaMail.jira@brutus>
	 <1228999708.27387.1289503355@webmail.messagingengine.com>
	 <509899e80812110450n3fd51e8cxca32b807f19bdec4@mail.gmail.com>
	 <ec6e67fd0812110457k399f7a1dm96a592563434d305@mail.gmail.com>
	 <1229000867.31643.1289505941@webmail.messagingengine.com>
	 <509899e80812110513n778a4792y1c85404bbe23b909@mail.gmail.com>
	 <ec6e67fd0812110519m5caed8f9h4a5ea6990ce16a89@mail.gmail.com>

------=_Part_7434_3924680.1229002616238
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Refresh my memory - what is it about wireTap that doesn't suit? (If
> you maybe swizzle your understanding of wire tap to be - send a copy
> of the same message to N destinations rather than just 2 :)
>
>
To me wireTap feels / sounds like a way to "tap into" a message, where the
*other* receivers are not the primary, ie, that there is one primary and
'tapped to' endpoints are secondary.

Think of MI5, FBI or AFP (aussie fed police) tapping your phone, they are
not the intended recipient of the message, but they get one (lots).

In a loan broker example, where we call out to multiple loan providers, they
are all the intended recipient, so the wireTap seems though it is not suited
for this position, based on it's name.

    "I don't want to "wire tap" a message to them, I want to send to all."

My current use of the <multicast> and in documentation I explain to others
kind of fits into a Blind (don't look at message) Recipient List.

.. hope that makes sense. (and the icon fits)
http://www.eaipatterns.com/RecipientList.html

------=_Part_7434_3924680.1229002616238--