Hi Gordon, <<Would the proton Messenger API meet your needs?
Yes, Proton is what we need, but if possible we do not want to use Proton directly because now only qpid libs is used in our application. Best way for us if qpidmessaging.dll will include Proton in full. Current our use case looks like 1. 1) Publish – Subscribe pattern: Sender à Scalable Cloud with federation à Receivers 2. 2) Point to point channel: Sender à Scalable Load Balanced Cloud with federation à Receiver 3. 3) Peer to Peer: Sender à Receiver (no cloud) We need P2P (#3) for 'simplified' messaging. Of course it is possible to have "P2P"-like connectivity with cloud but some time we need 'real' P2P'. Thanks for your information about qpidmessaging.dll, it was very useful to me ))) Regards, Alexander Yakovets On Wed, May 28, 2014 at 9:45 AM, Gordon Sim <g...@redhat.com> wrote: > On 05/27/2014 03:56 PM, Alexander Yakovets wrote: > >> 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? >> > > In theory it would certainly be *possible* to extend qpid::messaging to > allow incoming connections to be listened for and handled. Better > non-blcoking support would be needed as well. > > There is no plan as yet as to if or when this would be done however. > > Would the proton Messenger API meeet your needs? Note that you could > implement the 'server' with Messenger and the 'client(s)' with > qpid::messaging if desired. > > You may have seen my attempts to start a debate about the future direction > for the various APIs. If you can share any more detail about what you want > from an API and about your use case in general that would be interesting. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > For additional commands, e-mail: users-h...@qpid.apache.org > >
