You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by "Hickerson, David A" <da...@boeing.com> on 2011/03/10 01:33:36 UTC
What is the difference in the classes in qpid/client and
qpid/messaging in C++?
What is the difference between the classes in qpid/client and qpid/messaging in C++?
I have noticed that Connection is in each. For a client application, which is supposed to be used?
Some of the examples point to each and the documention seems to be more filled out for the messaging/ classes.
Thanks,
Dave
David Hickerson david.a.hickerson@boeing.com<ma...@boeing.com>
Senior Engineer phone: 719-235-3265
Mission Operations
The Boeing Company
1330 Inverness Dr., Suite 330
Colorado Springs, CO 80910
Re: What is the difference in the classes in qpid/client and qpid/messaging
in C++?
Posted by Gordon Sim <gs...@redhat.com>.
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
RE: What is the difference in the classes in qpid/client and
qpid/messaging in C++?
Posted by "Hickerson, David A" <da...@boeing.com>.
Is there a replacement for SubscriptionManager and AsyncSession?
-----Original Message-----
From: William Henry [mailto:whenry@redhat.com]
Sent: Thursday, March 10, 2011 8:25 AM
To: users@qpid.apache.org
Cc: users@qpid.apache.org
Subject: Re: What is the difference in the classes in qpid/client and qpid/messaging in C++?
On Mar 9, 2011, at 5:34 PM, "Hickerson, David A" <da...@boeing.com> wrote:
> What is the difference between the classes in qpid/client and qpid/messaging in C++?
One, qpid/client, is supporting the older API that doesn't have the new "addressing". Though you can have a qpid/client client send/receive messages to a qpid/messaging client, you obviously can't mix the APIs in the one client. (someone else can describe version numbers etc.)
Use qpid/messaging.
>
> I have noticed that Connection is in each. For a client application, which is supposed to be used?
>
> Some of the examples point to each and the documention seems to be more filled out for the messaging/ classes.
Yep, use that one.
William
>
> Thanks,
>
> Dave
>
> David Hickerson david.a.hickerson@boeing.com<ma...@boeing.com>
> Senior Engineer phone: 719-235-3265
> Mission Operations
> The Boeing Company
> 1330 Inverness Dr., Suite 330
> Colorado Springs, CO 80910
>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
Re: What is the difference in the classes in qpid/client and qpid/messaging in C++?
Posted by William Henry <wh...@redhat.com>.
On Mar 9, 2011, at 5:34 PM, "Hickerson, David A" <da...@boeing.com> wrote:
> What is the difference between the classes in qpid/client and qpid/messaging in C++?
One, qpid/client, is supporting the older API that doesn't have the new "addressing". Though you can have a qpid/client client send/receive messages to a qpid/messaging client, you obviously can't mix the APIs in the one client. (someone else can describe version numbers etc.)
Use qpid/messaging.
>
> I have noticed that Connection is in each. For a client application, which is supposed to be used?
>
> Some of the examples point to each and the documention seems to be more filled out for the messaging/ classes.
Yep, use that one.
William
>
> Thanks,
>
> Dave
>
> David Hickerson david.a.hickerson@boeing.com<ma...@boeing.com>
> Senior Engineer phone: 719-235-3265
> Mission Operations
> The Boeing Company
> 1330 Inverness Dr., Suite 330
> Colorado Springs, CO 80910
>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
Re: What is the difference in the classes in qpid/client and qpid/messaging
in C++?
Posted by Gordon Sim <gs...@redhat.com>.
On 03/10/2011 12:33 AM, Hickerson, David A wrote:
> What is the difference between the classes in qpid/client and qpid/messaging in C++?
>
> I have noticed that Connection is in each. For a client application, which is supposed to be used?
The qpid::messaging namespace is the one we recommend. That is the one
that future development will be focusing on. The qpid::client namespace
is an older client API.
> Some of the examples point to each and the documention seems to be more filled out for the messaging/ classes.
I've moved the old examples into an 'old_examples' directory to
hopefully make this a little clearer.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org