Hi Oleg
We are currently working on improving the blocking version of HTTP
connection management components in HttpConn module of HttpClient, but
certain adjustments in priorities in order to tackle HTTPCORE-25 first
is an option. Would you be interested in giving us a helping hand
developing / testing a non-blocking HTTP connection manager?
Let me take a look at this and see if I can handle it, as its of high
importance to us. If I am successful, I will share any code back with you.
HttpCore NIO has been designed to work with any arbitrary SocketChannel,
so adding SSL layer security should not be difficult. All it takes is
making sure the I/O reactor instantiates the appropriate channel when
connecting to a remote host or listening for incoming connections. The
best approach to achieve this would be to use the good ol' factory
pattern
I think there is more to do when using SSL with NIO. Check this ->
http://java.sun.com/j2se/1.5.0/docs/guide/security/jsse/JSSERefGuide.html#SSLENG
They state why a SSLSocketChannel class is not available with the JDK.
My understanding is that we need to tackle this with the
NHttpServiceHandler and NHttpClientHandler and use the SSLEngine class
provided by the JDK to decode the byte buffers read from the NW into the
application.
Please go ahead and open a feature request in JIRA. Alternatively you
may just want to subclass the default I/O reactor impls and to override
#connect() and #listen() methods.
I will wait for you reply to see how we should raise the JIRA
thanks
asankha
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
