Hi Gordon, On Wed, May 22, 2013 at 4:54 PM, Christian Fromme <[email protected]> wrote: > On Wed, May 22, 2013 at 4:16 PM, Gordon Sim <[email protected]> wrote: > >> First, I would not advise you to start developing against the qpid::client >> API as it is old, AMQP 0-10 specific and more complicated to use. Instead >> look at the qpid::messaging API. >> >> In qpid::messaging you subscribe by creating a receiver on the session, >> passing in an address to identify the source of messages and optionally some >> further properties for the subscription. > > I ended up using the qpid::client API because I didn't find a way to > subscribe to get messages pushed to a process via the qpid::messaging > API. Looking at it again after your advice now, I still don't really > know what to do. I see the routines you described, but how do I > register a callback or what interface do I need to implement in order > to get new messages pushed? Could you maybe point me to an example > please?
I just found this: http://qpid.2158936.n2.nabble.com/Best-Practices-for-C-API-td7481171.html And it sounds like there is no "push" style subscription in the qpid::messaging API (sad face). I'll take a look at the example you've attached back then. Christian --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
