On Jan 4, 2012, at 5:41 AM, Dejan Bosanac wrote: > nio+ssl should work exactly the same as the plain ssl transport, so this > SslBrokerService enhancement you're working is totally valid and we should > have it.
Okay I think I can make a simple test to show working ssl and non-working nio+ssl then. > The reason why socket factory isn't used in nio case is because it isn't > used by the java nio ssl API (if you hate ssl you'll hate nio+ssl even more > :) Why then do the NIO[SSL]* bits even have methods with *SocketFactory bits, is this due to extending the TCP bits? What is the NIO version of the SslSocketFactory muck? (I know jack about nio, only that it exists and uses buffers and channels). > We should provide the proper ssl context to the NIOSSLTransport > using setSslContext() method, so you might start with checking if the > correct context is being passed there. I'll look into it more when I have some time. > I'm looking forward to your further work in this area. Thanks for the detail :-) --jason
