Mailing-List: contact users-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@qpid.apache.org
Received-SPF: pass (nike.apache.org: domain of gsim@redhat.com designates
 209.132.183.28 as permitted sender)
Message-ID: <4CD12C76.3050307@redhat.com>
Date: Wed, 03 Nov 2010 09:33:42 +0000
From: Gordon Sim <gsim@redhat.com>
Organization: Registered Address: Red Hat UK Ltd, Amberley Place, 107-111
 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom.,Registered in
 England and Wales under Company Registration No. 3798903,Directors: Michael
 Cunningham (USA), Charlie Peters (USA) and David Owens (Ireland)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.9.1.9) Gecko/20100430 Fedora/3.0.4-2.fc11 Lightning/1.0b1
 Thunderbird/3.0.4
MIME-Version: 1.0
To: users@qpid.apache.org
Subject: Re: Publish-Subscribe queue question
References: <1288278508103-5682939.post@n2.nabble.com>
 <4CC9936D.80308@redhat.com> <1288280384405-5683098.post@n2.nabble.com>
 <4CC99A0A.6030104@redhat.com> <1288281194796-5683157.post@n2.nabble.com>
 <4CC99FC3.6060206@redhat.com> <1288313993558-5684875.post@n2.nabble.com>
 <4CCAB3F6.1000300@redhat.com> <1288659867794-5695668.post@n2.nabble.com>
 <4CD07E42.9060404@redhat.com> <1288747777410-5699801.post@n2.nabble.com>
In-Reply-To: <1288747777410-5699801.post@n2.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 11/03/2010 01:29 AM, zhaoyi0113@gmail.com wrote:
> I have read the example for pub-sub pattern. But it doesn't use Topic, it
> uses queues. What I want is to use a Topic for pub-sub. For example, if two
> subscribers subscribe on one queue, one message will only be delivered to
> one subscriber not both of them. How can I set up a Topic in old API?

The concept of a 'topic' as JMS defines it does not directly exist in 
AMQP 0-10. Rather it is constructed by creating an distinct exclusive 
subscription queue for each subscriber, binding that to an exchange and 
then subscribing to that queue. Messages published to this exchange then 
get routed to each subscription queue and thus each subscriber sees each 
message. The subscribers are not sharing a queue, they each have their 
own queue.

When you use the Qpid JMS client, and you use a Topic, it is doing this 
work for you. The broker doesn't see a topic being used, it sees a queue 
created for each subscriber and then being bound to an exchange.

The old c++ API did not have that same functionality built in to it, so 
the application developer needed to go through the steps manually as in 
the pub-sub example. In the pub-sub example you can start multiple 
lilsteners and then when you publish messages, each listener will 
receive every published message it is interested in. This is the same 
pattern of message flow as generally implied by a JMS Topic, and the 
brokers view is the same in each case.

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org