qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gordon Sim <g...@redhat.com>
Subject Re: What is the difference in the classes in qpid/client and qpid/messaging in C++?
Date Fri, 11 Mar 2011 18:13:54 GMT
On 03/10/2011 10:53 PM, Hickerson, David A wrote:
> Is there a replacement for SubscriptionManager and AsyncSession?

Not a direct replacement, no. The messaging API is at a higher level of 
abstraction than the AMQP 0-10 oriented client namespace API was.

Operations like send() and acknowledge() have flags that control whether 
it is synchronous or synchronous.

In place of subscriptions the messaging API has receivers with which you 
fetch messages (prefetch can be controlled via the receivers capacity). 
You can use the Session::nextReceiver() call to service several 
receivers with a single thread. Dispatching the messages via some 
listener/callback interface is then a fairly trivial task. (We do 
anticipate some direct support there at some time in the future, but for 
now its usually simple enough for applications to build it in themselves).

Hope this helps. Have a read through the programming guide and please 
feel free to ask any questions you have.

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


Mime
View raw message