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: [email protected] 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:[email protected]] Sent: Tuesday, November 13, 2012 10:50 PM To: [email protected] 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: [email protected] For additional commands, e-mail: [email protected]
