Thanks Gordon, I agree it looks like qpidmessaging.dll from qpid 0.26 with proton 0.6 do not support listening for incoming connection client but maybe future versions will be capable for this? Does qpid architecture suppose this functionality? Or any communication via qpid::messaging API must include broker?
Regards, Alexander Yakovets On Tue, May 27, 2014 at 2:46 AM, Gordon Sim <[email protected]> wrote: > On 05/26/2014 09:44 PM, Alexander Yakovets wrote: > >> I can see qpid-proton.dll is included in >> qpid-messaging.dll and I think it should be possible to get connected 2 >> peers with qpidmessaging.dll without any broker running. But I failed to >> get this connectivity, looks like every time I need broker running. If >> broker is ON, AMPQ 1.0 based connectivity is ok, if broker is OFF >> connection not established. >> > > The issue here is that the qpid::messaging API does not expose any way of > listening for incoming connections. It only offers the ability to establish > outgoing connections. > > To write a component that accepts incoming connections you will need to > use a different API (and handle connections that were initiated by the > peer, rather than the application code). The simplest option there is the > proton Messenger API. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
