AsynchronousSocketChannel still throws unspecified exception (original) (raw)
Alan Bateman Alan.Bateman at oracle.com
Wed Jul 13 01:55:26 PDT 2011
- Previous message: AsynchronousSocketChannel still throws unspecified exception
- Next message: AsynchronousSocketChannel still throws unspecified exception
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
cowwoc wrote:
: Now I'm getting really worried... I just noticed that socket timeouts are wrong as well!
If you recall, we had agreed that a timeout value of 0 or less should mean "no timeout" and Long.MAXVALUE should mean "wait forever": http://web.archiveorange.com/archive/v/gpYtBv5dfSke8QjCflUY Yes, I remember that discussion and we changed it, via 6878369, so that <= 0 means that the I/O operation doesn't have a timeout (previously it was specified to throw IllegalArgumentException if a negative timeout was specified).
-Alan.
- Previous message: AsynchronousSocketChannel still throws unspecified exception
- Next message: AsynchronousSocketChannel still throws unspecified exception
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]