[
https://issues.apache.org/jira/browse/DIRMINA-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570549#action_12570549
]
Trustin Lee commented on DIRMINA-526:
-------------------------------------
Exposing getCurrentWriteRequest() and updating the write counter immediate
should be considered as a different issue. Anyways, let's update the counter
more frequently, and keep discussing about exposing getCurrentWriteRequest().
> Expose getCurrentWriteRequest() via IoSession
> ---------------------------------------------
>
> Key: DIRMINA-526
> URL: https://issues.apache.org/jira/browse/DIRMINA-526
> Project: MINA
> Issue Type: Improvement
> Components: Core
> Environment: jdk1.6.0_03 Linux x64
> Reporter: Geoff Cadien
> Assignee: Mike Heath
> Fix For: 2.0.0-M1
>
>
> 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.
