AsynchronousSocketChannel still throws unspecified exception (original) (raw)

Alan Bateman Alan.Bateman at oracle.com
Wed Jul 13 14:06:38 PDT 2011

cowwoc wrote:

: I've provided you with many concrete reasons why treating timeout <= 0 as "return immediately" is the right way to go Yes, and this is useful as it's attempting to use the API in a different way that it was envisaged.

:

PS: You don't need to actually implement timeout <= 0 as returning available bytes. All you need to do is put it in the specification and return 0 for now (as if there are no available bytes). We can improve the implementation later on. I'm mostly worried about the specification here. We can't change this for jdk7 but we what we can do is decide the right solution for jdk8.

-Alan.

More information about the nio-dev mailing list