You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Trustin Lee (JIRA)" <ji...@apache.org> on 2007/09/28 17:52:51 UTC

[jira] Updated: (DIRMINA-249) exceptionCaught() should provide more information

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

Trustin Lee updated DIRMINA-249:
--------------------------------

    Affects Version/s:     (was: 0.9.4)
        Fix Version/s: 2.0.0-M1

This can introduce some changes in the core API, so let's resolve it in 2.0.0-M1.

> exceptionCaught() should provide more information
> -------------------------------------------------
>
>                 Key: DIRMINA-249
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-249
>             Project: MINA
>          Issue Type: Improvement
>         Environment: All
>            Reporter: Vinod Panicker
>             Fix For: 2.0.0-M1
>
>
> Currently if the application calls a write() on MINA, it will get notified of any exceptions via the exceptionCaught() method.  The problem is that the application does not have any information as to what data could not be written on the session.  To figure that out, it either has to wait on the WriteFuture or implement some state mechanism within the IoSession.
> Trustin recommended that a WriteException could be created, which could provide the necessary information. It should have the ByteBuffer for which the write() failed.

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