You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Geoff Cadien (JIRA)" <ji...@apache.org> on 2008/02/01 22:49:08 UTC
[jira] Created: (DIRMINA-526) Expose getCurrentWriteRequest() via
IoSession
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
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.
[jira] Updated: (DIRMINA-526) Expose getCurrentWriteRequest() via
IoSession
Posted by "Mike Heath (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRMINA-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Heath updated DIRMINA-526:
-------------------------------
Fix Version/s: (was: 2.0.0-M1)
2.0.0-M2
> 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-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.
[jira] Commented: (DIRMINA-526) Expose getCurrentWriteRequest() via
IoSession
Posted by "Trustin Lee (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Closed: (DIRMINA-526) Expose getCurrentWriteRequest() via
IoSession
Posted by "Julien Vermillard (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRMINA-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julien Vermillard closed DIRMINA-526.
-------------------------------------
> 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.
[jira] Updated: (DIRMINA-526) Expose getCurrentWriteRequest() via
IoSession
Posted by "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 updated DIRMINA-526:
--------------------------------
Affects Version/s: 2.0.0-M1
> 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.
[jira] Assigned: (DIRMINA-526) Expose getCurrentWriteRequest() via
IoSession
Posted by "Mike Heath (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRMINA-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Heath reassigned DIRMINA-526:
----------------------------------
Assignee: Mike Heath
> 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.
[jira] Resolved: (DIRMINA-526) Expose getCurrentWriteRequest() via
IoSession
Posted by "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.