RFR 8224477 [13] java.net.Socket::setOption - implementation mismatch to spec
Chris Hegarty
chris.hegarty at oracle.com
Mon May 27 10:48:28 UTC 2019
On 24/05/2019 08:28, Alan Bateman wrote:
> On 23/05/2019 17:32, Chris Hegarty wrote:
>> ...
This next iteration addresses all of Alan's comments and suggestions.
Additionally, while here we can take the opportunity to cleanup the spec
inconsistencies of the getOption/setOption methods across the socket
impls. The current default implementation is also problematic,
undocumented and unspecified. It is highly questionable for code to
depend on it. The default implementation can be simplified, specified,
and a note advising subclasses to override added. ( The CSR contains
specifics, that I won't duplicate here )
Updated webrev:
https://cr.openjdk.java.net/~chegar/8224477/webrev.03/
CSR:
https://bugs.openjdk.java.net/browse/JDK-8224792
-Chris.
More information about the net-dev
mailing list