AsynchronousSocketChannel still throws unspecified exception

[cowwoc]

     Fair enough. I understand that we're too far along the JDK7 release 
schedule.

Thanks,
Gili

On 13/07/2011 5:08 PM, Alan Bateman-2 [via nio-dev] wrote:
> 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.
>
>
>
> ------------------------------------------------------------------------
> If you reply to this email, your message will be added to the 
> discussion below:
> http://nio-dev.3157472.n2.nabble.com/AsynchronousSocketChannel-still-throws-unspecified-exception-tp6471557p6580775.html 
>
> To unsubscribe from AsynchronousSocketChannel still throws unspecified 
> exception, click here 
> <http://nio-dev.3157472.n2.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=6471557&code=Y293d29jQGJicy5kYXJrdGVjaC5vcmd8NjQ3MTU1N3wxNTc0MzIxMjQ3>. 
>



--
View this message in context: http://nio-dev.3157472.n2.nabble.com/AsynchronousSocketChannel-still-throws-unspecified-exception-tp6471557p6589792.html
Sent from the nio-dev mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/nio-dev/attachments/20110716/56c4e4da/attachment.html