7042979: Rename StandardSocketOption and StandardWatchEventKind
Rémi Forax
forax at univ-mlv.fr
Mon May 9 03:09:19 PDT 2011
On 05/09/2011 11:39 AM, Alan Bateman wrote:
>
> The recent discussion on whether the class defining the standard
> charsets be named StandardCharset or StandardCharsets raises the
> question for three other classes that are also new in jdk7:
>
> java.net.StandardSocketOption
> java.nio.file.StandardWatchEventKind
> com.sun.nio.sctp.SctpStandardSocketOption (part of the SCTP API)
>
> Given the decision to rename StandardCharset it would be inconsistent
> if we didn't rename these too. To that end, and disruptive as it might
> be, the webrev with the changes is here:
> http://cr.openjdk.java.net/~alanb/7042979/webrev/
>
> Thanks,
>
> -Alan.
>
Hi Alan,
It's ok for me.
I see that you have changed the context's type of
StandardWatcheventKinds.OVERFLOW
from Void to Object to allow implementation specific context. Am I right ?
Rémi
More information about the nio-dev
mailing list