Hi Toby, Thanks for the feedback.
Do you mean that the socket_engine has been removed after version 0.12.2? hmmm...this is not a viable solution because now it means that you are stuck with that version and can't benefit from bugs fixes, improvements etc from newer versions, right? I will have a look at it anyway, but it seems to me that as of today qpid proton has not been designed to be easily integrated in other io frameworks, which is a pity. One solution I can think of in my framework for a qpid producer/publisher client is to create a specific ACE task in a separate thread and communicate with that task/thread with an ACE queue (each time a message is inserted into the queue, ACE will wake up the ACE task), that would be the easiest as I won't have to dig into qpid io framework. But for a consumer client, I have to have some kind of mechanism to trigger an ACE event and from there call qpid proton....I will have a look at your solution, but it does not look very straightforward to me, maybe because the proton io interface is still a little bit obscure imwo. Also, as you mentionned, no security layers, which can be annoying as well as my app is communicating with a server that is abroad... Cheers, Faycal On Sat, Jul 9, 2016 at 1:42 AM, Tobias Duckworth <[email protected]> wrote: > Hi, > > I am also new to qpid-proton and needed to achieve a similar thing to you. > > I found the most recent releases 0.14 snapshot and 0.13.0 weren't very easy > to interface with for the purposes you describe. > > I ended up using 0.12.2, which has a socket_engine > (proton-c/bindings/cpp/include/proton/io.hpp). > With this you can either get the socket engine to connect to your URL, or > you can just provide the socket descriptor as a constructor parameter. > Then you can 'drive' the engine either by calling the run() function on a > thread (which isn't very useful for integrating into your own io > framework), > or by implementing the proton::handler interface in such a way that it is > executed on the thread you wish to do the work on. > > It all works very nicely once you get it right, apart from I can't get any > of the security layers to work at present, so no ssl or sasl yet. > > Good luck, > Toby > > > > > -- > View this message in context: > http://qpid.2158936.n2.nabble.com/Fwd-qpid-proton-integration-with-other-event-loops-i-e-QT-and-ACE-tp7647033p7647096.html > Sent from the Apache Qpid users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
