You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Galen O'Sullivan (JIRA)" <ji...@apache.org> on 2018/05/11 18:05:00 UTC

[jira] [Commented] (GEODE-2113) Implement SSL over NIO

    [ https://issues.apache.org/jira/browse/GEODE-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16472379#comment-16472379 ] 

Galen O'Sullivan commented on GEODE-2113:
-----------------------------------------

There is a real win here for TcpConduit. TcpConduit uses oio for SSL and nio for non-SSL, which results in different behavior in those two cases. If we switched SSL to nio, we could eliminate a lot of code, make cluster messaging more consistent, and make cluster messaging faster.

Perhaps we can create separate subtasks for TcpConduit, CacheServer, TcpServer (and maybe even the client?)

> Implement SSL over NIO
> ----------------------
>
>                 Key: GEODE-2113
>                 URL: https://issues.apache.org/jira/browse/GEODE-2113
>             Project: Geode
>          Issue Type: Improvement
>          Components: messaging
>            Reporter: Addison
>            Priority: Major
>
> Java now has a nifty javax.net.ssl.SSLSocketFactory that can produce an SSLSocket from an existing Socket.  This will let us create an SSLSocket that has an NIO SocketChannel and get rid of all of the "Old IO" code.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)