[
https://issues.apache.org/jira/browse/IGNITE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15308043#comment-15308043
]
Dmitry Karachentsev commented on IGNITE-3054:
---------------------------------------------
Working on SSL support. To keep it compatible, and in same time support
switching clients to unblocking mode, there needs to be added SSL handshake
support from GridNioSslHandler and encrypt/decrypt methods for server
connections.
This solution picked because of it's unable to use GridNioServer, it's designed
to work in non-blocking mode, but we want to keep current server communication
logic untouched (use blocking mode and thread per connection). In previous
implementation SSLServerSocketFactory was used, which is not applicable for NIO.
Left:
* SSL support.
* Performance tests.
> Rework client connection handling from thread-per-client to NIO model.
> ----------------------------------------------------------------------
>
> Key: IGNITE-3054
> URL: https://issues.apache.org/jira/browse/IGNITE-3054
> Project: Ignite
> Issue Type: Task
> Components: general
> Affects Versions: 1.5.0.final
> Reporter: Vladimir Ozerov
> Assignee: Dmitry Karachentsev
> Priority: Blocker
> Fix For: 1.7
>
>
> Currently both servers and clients has the same operational model -
> thread-per-connection. While being more or less fine for servers, this could
> be a problem for clients when their total number is too high (e.g. 1000 or
> even more).
> We should rework client handling model and employ standard NIO technique: one
> or several acceptor threads + thread pool to server requests.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
