adding rsockets support into JDK

[Lu, Yingqi]

Hi Chris,

Thank you for your feedback.

I was following the suggestion [1] from Joe Darcy to move the RDMA factory methods from jdk.net.Sockets to jdk.net.RDMASockets. 

I will remove setOption and getOption methods from jdk.net.RdmaSockets in the next version of the patch. At the meantime, please let me know if there is anything else missing from the current version.

Thanks,
Lucy

[1] https://bugs.openjdk.java.net/browse/JDK-8205186

>-----Original Message-----
>From: Chris Hegarty [mailto:chris.hegarty at oracle.com]
>Sent: Wednesday, November 14, 2018 12:31 AM
>To: Lu, Yingqi <yingqi.lu at intel.com>
>Cc: nio-dev at openjdk.java.net; Viswanathan, Sandhya
><sandhya.viswanathan at intel.com>; Aundhe, Shirish
><shirish.aundhe at intel.com>; Kaczmarek, Eric <eric.kaczmarek at intel.com>
>Subject: Re: adding rsockets support into JDK
>
>
>> On 14 Nov 2018, at 00:50, Lu, Yingqi <yingqi.lu at intel.com> wrote:
>>
>> Hi All,
>>
>> Here is the version 16 of the patch:
>http://cr.openjdk.java.net/~ylu/8195160.16.
>
>This looks much better.
>
>Just an initial comment. Why move the factory methods, from jdk.net.Sockets
>to jdk.net.RdmaSockets? It is fine to do this, just curious why.
>
>I don’t think that jdk.net.RdmaSockets needs the static methods for setting
>and retrieving the socket options. That can be done through the Socket type
>itself.  jdk.net.Sockets contains such methods as they predate the more
>general option support on the socket type itself. There are plans afoot to
>deprecate these from jdk.net.Sockets as they are no longer needed, see
>8189744 [1].
>
>-Chris.
>
>[1] https://bugs.openjdk.java.net/browse/JDK-8189744