Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 6750 invoked from network); 21 Apr 2008 02:35:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 Apr 2008 02:35:18 -0000 Received: (qmail 95112 invoked by uid 500); 21 Apr 2008 02:35:18 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 95083 invoked by uid 500); 21 Apr 2008 02:35:18 -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 95074 invoked by uid 99); 21 Apr 2008 02:35:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 20 Apr 2008 19:35:18 -0700 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 (athena.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; Mon, 21 Apr 2008 02:34:33 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1Jnlri-0003Ed-9H for dev@activemq.apache.org; Sun, 20 Apr 2008 19:34:46 -0700 Message-ID: <16801738.post@talk.nabble.com> Date: Sun, 20 Apr 2008 19:34:46 -0700 (PDT) From: chicagoclimber To: dev@activemq.apache.org Subject: How many destinations can one subscription have? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: chicagoclimber@gmail.com X-Virus-Checked: Checked by ClamAV on apache.org Hi, I've been looking through the code trying to understand the overall architecture of the application --- and I came across something that seems somewhat inconsistent. >From what I understand, one subscription (org.apache.activemq.broker.region.AbstractSubscription) can be added to multiple physical destinations (org.apache.activemq.broker.region.Destination) by using wildcards in the name of the destination (org.apache.activemq.command.ActiveMQDestination). When new consumer is added (AbstractRegion.addConsumer()), the same subscription object is added to multiple matching destinations. Now, in r635682, rajdavies added destination property to AbstractSubscription. This destination is the physical destination, not ActiveMQDestination. This doesn't seem to make sense ... at least not to me. Can someone explain this? Thanks! -sergey -- View this message in context: http://www.nabble.com/How-many-destinations-can-one-subscription-have--tp16801738s2354p16801738.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.