On Fri, 2016-07-08 at 17:26 +0100, Tobias Duckworth wrote: > Hi, > > I've used qpid-proton-0.12.2 in my application as a connection_engine > or > io::socket_engine. I need to arrange for the connect and > reading/writing > to happen asynchronously and my implementation sits within an > existing > io framework. > > Everything has integrated quite nicely, apart from SSL, which I > cannot > get to work. > > I have some straightforward C++ examples, one of which derives from > connection_engine, and the other from container. I can see that for > the > container example ssl_init gets called from connection_options.cpp > and > everything then works nicely, whereas for the connection_engine > example > it does not. > > The problem seems to be that for the connection_engine build > 'outbound' > is not set, and therefore ssl_init does not get called. > > Please could someone explain how to implement an amqp client using > the > connection_engine framework that supports SSL?
Known problem: https://issues.apache.org/jira/browse/PROTON-1255 You are motivating me to fix it. There is another alternative: you can establish the secure stream (SSL) outside of proton, and ignore proton's SSL support. If you try this please report on the JIRA any problems you run into. The goal is for connection_engine to support both. I'd appreciate your help verifying the fix, if you want to put a watch on the JIRA. I've got some other stuff distracting me but this is my top priority on proton now. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
