Mailing-List: contact users-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@qpid.apache.org
Received-SPF: pass (athena.apache.org: domain of gsim@redhat.com designates
 209.132.183.28 as permitted sender)
Message-ID: <4E8C1500.8040800@redhat.com>
Date: Wed, 05 Oct 2011 09:27:44 +0100
From: Gordon Sim <gsim@redhat.com>
Organization: Red Hat UK Ltd, Registered in England and Wales under Company
 Registration No. 3798903, Directors: Michael Cunningham (USA), Mark Hegarty
 (Ireland), Matt Parsons (USA), Charlie Peters (USA)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.9.1.15) Gecko/20101027 Fedora/3.0.10-1.fc12 Lightning/1.0b1
 Thunderbird/3.0.10
MIME-Version: 1.0
To: users@qpid.apache.org
Subject: Re: problem with Qpidd
References: 
 <CAJuTaCNEtBgOxdP7fQrXZb_By3hXaUof_k=Q7wb0GWan-g4QdA@mail.gmail.com>
 <4E8421DE.9090602@redhat.com>
 <CAJuTaCMBVGR0iFdK=AMcz1NGZzL9S_8T+B8F+1TL_ZNpKQk0gA@mail.gmail.com>
 <4E8445DB.5010103@redhat.com>
 <CAJuTaCMJsVL5i=fMEQnQgneKWOiRFNkxZHC7LJOKBZcnV+ZK1A@mail.gmail.com>
 <4E8451C4.8010208@redhat.com>
 <CAJuTaCNOvCaYh8uGn5HTkMFJ_efuJ_EDW25nty3VFWDd7wt=KA@mail.gmail.com>
 <4E845C7E.3030708@redhat.com>
 <CAJuTaCPcy+qNYzEOfH=savRmRgV=uunKRnq3r=PTdHqXU2a6Vg@mail.gmail.com>
 <4E847CFB.30305@redhat.com>
 <CAJuTaCMy5bVCWu_voVKOFYc9L1Wf3hzGDgv+9=na-3gFyUS_Tw@mail.gmail.com>
In-Reply-To: 
 <CAJuTaCMy5bVCWu_voVKOFYc9L1Wf3hzGDgv+9=na-3gFyUS_Tw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 09/30/2011 06:37 AM, surya prakash wrote:
> In qpid::messaging API i didn't found queue declare things ,so that i moved
> to qpid::client API

For creating queues you have a number of options to chose from depending 
on the different use cases.

(1) For pub-sub subscriptions, the library will take care of the declare 
and bind for you. So if you wish to get all messages matching a 
particular key - say my-key, sent to a particular exchange - say 
my-exchange -  you simply create a receiver with address 
'my-exchange/my-key'. (You can use the same address for senders of course).

(2) To create a response queue in a request-response pattern, the 
address options allow you to have the queue created on demand when 
opening the receiver (or indeed a sender, though less obviously useful 
in this particular pattern). This approach also lets you control the 
underlying declare (in the case of AMQP 0-10) E.g. you can create a 
receiver for the address 'my-queue; {create: always, 
node:{x-declare:{auto-delete:True}}}'

(3) You can use the qpid-config tool to create exchanges, queues and 
bindings statically, separate from your application logic. This is often 
a good idea.

(4) The tools as above use a message-based protocol - QMF - which you 
can also use directly (or through a separate QMF API). This is an area 
that needs better documentation but the following mail should provide 
sufficient pointers should this be appropriate to your needs: 
http://apache-qpid-users.2158936.n2.nabble.com/Delete-queue-exchange-binding-from-C-client-tp6472921p6473491.html

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