Strange Exception at read
Alan.Bateman at Sun.COM
Thu Nov 12 02:26:32 PST 2009
> Hi Alan,
> After tired the aio Socket channel and File channel, I found those use
> different Exception process way seperately.
> For some os error , File channel use some Exception classes, but
> Socket channel use IOException with os error message. The later hard
> to determinate to advance processing.
> There have some plan to unify those exceptions with os error?
I'm aware of a couple of cases (AsynchronousSocketChannel.connect on
Windows for example) where we don't translate the OS error with the
result that we throw an IOException rather than the more specific
ConnectException that SocketChannel and legacy Socket might throw. Is
that what you are thinking about?
More information about the nio-dev