RFR: 8255758: JEP 380 spec clarifications

[Michael McMahon]

On Tue, 3 Nov 2020 09:09:18 GMT, Daniel Fuchs <dfuchs at openjdk.org> wrote:

>> Minor spec changes from spec approved in initial CSR
>
> src/java.base/share/classes/java/net/doc-files/net-properties.html line 246:
> 
>> 244: <H2>Unix domain sockets</H2>
>> 245: <P>There are a number of system (and networking) properties that affect the behavior of
>> 246: channels to <i>Unix domain</i> server sockets when binding <i>automatically</i>.
> 
> Should this also mention <i>implicit</i> binding?

I'm not sure, as the system properties don't affect implicit binding, but I would have liked to have a place to "explain" all aspects of binding of Unix domain sockets/server-sockets. Maybe, I could add a paragraph at the end, just as an aside or note.

> src/java.base/share/classes/java/net/doc-files/net-properties.html line 250:
> 
>> 248: Automatic binding of a server socket occurs when {@link 
>> 249: java.nio.channels.ServerSocketChannel#bind(SocketAddress,int) ServerSocketChannel.bind}
>> 250: is called with a {@code null} address parameter. In this case, the system
> 
> doesn't it also happen when it is called with a UnixDomainSocketAddress that has an empty path?

No, an empty path signifies an unnamed address and only client sockets (SocketChannels) are allowed to be unnamed.

-------------

PR: https://git.openjdk.java.net/jdk/pull/1021