[jira] [Commented] (IGNITE-3054) Rework client connection handling from thread-per-client to NIO model.

["Konstantin Dudkov (JIRA)" <ji...@apache.org>]

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

Konstantin Dudkov commented on IGNITE-3054:
-------------------------------------------

Implemented input/ouput streams in BlockingSslHandler and test for it


> 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: Semen Boikov
>             Fix For: 2.1
>
>
> 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.15#6346)