RFR [9] 8044773: Refactor jdk.net API so that it can be moved out of the base module

Chris Hegarty chris.hegarty at oracle.com
Wed Apr 27 09:04:30 UTC 2016

On 26 Apr 2016, at 18:21, Alan Bateman <Alan.Bateman at oracle.com> wrote:

> I took a second pass over it. One thing that I'm wondering about is whether BaseExtendedSocketOptions + Support should be collapsed into one abstract class ExtendedSocketOptions (or better name) with 3 instance methods and 2 static methods. It's an internal interface so not a big deal but I think it would be a bit cleaner and allowed the oddly named "Support" to go away.

This works out quite nice.  Webrev updated in-place:

With this refactoring, and the reduced number of types over the various
iterations, I think we can remove the ‘Base' prefix and use the simpler
name sun.net.ext.ExtendedSocketOptions ( conflict with
jdk.net.ExtendedSocketOptions is less of an issue ).


More information about the build-dev mailing list