[jira] Resolved: (DIRMINA-526) Expose getCurrentWriteRequest() via IoSession

["Trustin Lee (JIRA)" <ji...@apache.org>]

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

Trustin Lee resolved DIRMINA-526.
---------------------------------

    Resolution: Fixed
      Assignee: Trustin Lee  (was: Mike Heath)

Now you have two public methods: IoSession.getCurrentWriteMessage() and IoSession.getCurrentWritteRequest(), which should address your issue along with DIRMINA-552.

> Expose getCurrentWriteRequest() via IoSession
> ---------------------------------------------
>
>                 Key: DIRMINA-526
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-526
>             Project: MINA
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 2.0.0-M1
>         Environment: jdk1.6.0_03 Linux x64
>            Reporter: Geoff Cadien
>            Assignee: Trustin Lee
>             Fix For: 2.0.0-M2
>
>
> It would be helpful is the protected method getCurrentWriteRequest() was exposed in the IoSession interface.  Currently when a client closes a connection before the message is completely sent there is no way to find out how much data was acutally sent before the connection was closed.  If getCurrentWriteRequest was exposed via IoSession it could be checked in sessionClosed to see if it is non-null and how many bytes are were actually sent could be determined.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.