You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Matjaž Ostroveršnik <Ma...@halcom.si> on 2012/11/13 21:09:46 UTC
client or messaging ?
Hi all,
Could somebody give me a hint how to implement a listener?
I know there is a MessageListener class which needs to be sub classed to do that, but this class in in qpid::client namespace.
The rest of the application uses qpid::messaging classes (including session and message).
1. It qpid::messaging a right choice or should we rather use qpid::client?
2. If qpid::messaging is a right choice, how can I implement a listener?
3. Why do we have two namespaces of classes with partially overlapping functionality?
4. When to use qpid::client and when qpid::messaging?
Thanks in advance
Matjaž
Re: client or messaging ?
Posted by Gordon Sim <gs...@redhat.com>.
On 11/13/2012 11:03 PM, Jakub Scholz wrote:
> Here is a simple message receiver which might inspire you:
> http://pastebin.com/CEXP8dzu ... (I'm not saying this is the best / perfect
> solution ... but it may work for you...).
Attached is an alternative example in case it is also useful.
RE: client or messaging ?
Posted by Matjaž Ostroveršnik <Ma...@halcom.si>.
It's a realy good example. I can learn a lot. Shouldn't be this part of the regular qpid documentation?
_________________________________
-----Original Message-----
From: Jakub Scholz [mailto:jakub@scholz.cz]
Sent: Wednesday, November 14, 2012 12:04 AM
To: users@qpid.apache.org
Subject: Re: client or messaging ?
Hi Matjaz,
Here is a simple message receiver which might inspire you:
http://pastebin.com/CEXP8dzu ... (I'm not saying this is the best / perfect
solution ... but it may work for you...).
Regards
Jakub
On Tue, Nov 13, 2012 at 9:09 PM, Matjaž Ostroveršnik <
Matjaz.Ostroversnik@halcom.si> wrote:
> Hi all,
>
> Could somebody give me a hint how to implement a listener?
> I know there is a MessageListener class which needs to be sub classed to
> do that, but this class in in qpid::client namespace.
> The rest of the application uses qpid::messaging classes (including
> session and message).
>
>
> 1. It qpid::messaging a right choice or should we rather use
> qpid::client?
>
> 2. If qpid::messaging is a right choice, how can I implement a
> listener?
>
> 3. Why do we have two namespaces of classes with partially
> overlapping functionality?
>
> 4. When to use qpid::client and when qpid::messaging?
>
> Thanks in advance
>
> Matjaž
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: client or messaging ?
Posted by Jakub Scholz <ja...@scholz.cz>.
Hi Matjaz,
Here is a simple message receiver which might inspire you:
http://pastebin.com/CEXP8dzu ... (I'm not saying this is the best / perfect
solution ... but it may work for you...).
Regards
Jakub
On Tue, Nov 13, 2012 at 9:09 PM, Matjaž Ostroveršnik <
Matjaz.Ostroversnik@halcom.si> wrote:
> Hi all,
>
> Could somebody give me a hint how to implement a listener?
> I know there is a MessageListener class which needs to be sub classed to
> do that, but this class in in qpid::client namespace.
> The rest of the application uses qpid::messaging classes (including
> session and message).
>
>
> 1. It qpid::messaging a right choice or should we rather use
> qpid::client?
>
> 2. If qpid::messaging is a right choice, how can I implement a
> listener?
>
> 3. Why do we have two namespaces of classes with partially
> overlapping functionality?
>
> 4. When to use qpid::client and when qpid::messaging?
>
> Thanks in advance
>
> Matjaž
>
RE: client or messaging ?
Posted by Matjaž Ostroveršnik <Ma...@halcom.si>.
Thank you for your fast answer. I'll stick with messaging. :-)
dr. Matjaž Ostroveršnik
direktor / Director
Poslovno področje Klirinški sistemi / Business Unit Clearing Systems
_________________________________
E: Matjaz.Ostroversnik@halcom.si
T: +386 1 2003352
F: +386 1 2003356
M: +386 31 307983
Halcom d.d.
Tržaška cesta 118,
1000 Ljubljana, Slovenija
www.halcom.si
_________________________________
-----Original Message-----
From: Darryl L. Pierce [mailto:dpierce@redhat.com]
Sent: Tuesday, November 13, 2012 10:50 PM
To: users@qpid.apache.org
Subject: Re: client or messaging ?
On Tue, Nov 13, 2012 at 08:09:46PM +0000, Matjaž Ostroveršnik wrote:
> Hi all,
>
> Could somebody give me a hint how to implement a listener?
> I know there is a MessageListener class which needs to be sub classed to do that, but this class in in qpid::client namespace.
> The rest of the application uses qpid::messaging classes (including session and message).
>
>
> 1. It qpid::messaging a right choice or should we rather use qpid::client?
The qpid::messaging APIs are the proper ones to use.
> 2. If qpid::messaging is a right choice, how can I implement a listener?
A good starting point would be to look at the C++ examples in
examples/messaging, such as client.cpp.
> 3. Why do we have two namespaces of classes with partially overlapping functionality?
qpid::client is the older APIs and no longer used. qpid::messaging is
the newer, better done API set that you should use.
> 4. When to use qpid::client and when qpid::messaging?
See above.
--
Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc.
Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: client or messaging ?
Posted by "Darryl L. Pierce" <dp...@redhat.com>.
On Tue, Nov 13, 2012 at 08:09:46PM +0000, Matjaž Ostroveršnik wrote:
> Hi all,
>
> Could somebody give me a hint how to implement a listener?
> I know there is a MessageListener class which needs to be sub classed to do that, but this class in in qpid::client namespace.
> The rest of the application uses qpid::messaging classes (including session and message).
>
>
> 1. It qpid::messaging a right choice or should we rather use qpid::client?
The qpid::messaging APIs are the proper ones to use.
> 2. If qpid::messaging is a right choice, how can I implement a listener?
A good starting point would be to look at the C++ examples in
examples/messaging, such as client.cpp.
> 3. Why do we have two namespaces of classes with partially overlapping functionality?
qpid::client is the older APIs and no longer used. qpid::messaging is
the newer, better done API set that you should use.
> 4. When to use qpid::client and when qpid::messaging?
See above.
--
Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc.
Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/