[jira] [Resolved] (SSHD-636) Allow to override socket.write method in Nio2Session

["Goldstein Lyor (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SSHD-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Goldstein Lyor resolved SSHD-636.
---------------------------------
       Resolution: Fixed
         Assignee: Goldstein Lyor
    Fix Version/s: 1.2.0

> Allow to override socket.write method in Nio2Session
> ----------------------------------------------------
>
>                 Key: SSHD-636
>                 URL: https://issues.apache.org/jira/browse/SSHD-636
>             Project: MINA SSHD
>          Issue Type: Improvement
>    Affects Versions: 1.0.0
>            Reporter: Eugene Petrenko
>            Assignee: Goldstein Lyor
>            Priority: Minor
>             Fix For: 1.2.0
>
>
> There is a good method where reading is started: {{org.apache.sshd.common.io.nio2.Nio2Session#doReadCycle(java.nio.ByteBuffer, org.apache.sshd.common.io.nio2.Nio2CompletionHandler<java.lang.Integer,java.lang.Object>)}} 
> It could be nice to have similar signature method for writing. 
> My main goal is to include better logging MDC context for each callback. This allows to split logging per client, thus making it possible to figure out what a particular client/connection was working on 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)