Adding values to enum java.net.StandardProtocolFamily

Florian Weimer fweimer at redhat.com
Thu Feb 13 07:04:50 PST 2014


On 02/13/2014 03:23 PM, David M. Lloyd wrote:

>> Okay, sounds reasonable.  The PF_LOCAL protocol family is not available
>> with Winsock, so I guess it will have to be a separate enum then, with a
>> single member, although OpenJDK already requires PF_LOCAL support on the
>> non-Windows platforms.
>
> Windows "named pipes" seem similar enough to UNIX sockets for a uniform
> implementation (full-duplex, socket-like connection, byte- or
> message-oriented, reliable delivery, file-like API, to list a few things
> off of wikipedia).  It was my intent to support them in XNIO on Windows
> at some point, equivalently to UNIX sockets on other OSes, which I
> already have some support for.

Naming is fundamentally different.  With that caveat, it would be 
possible to expose a socket-based interface, but application code would 
have to adhere to the platform naming convention.

-- 
Florian Weimer / Red Hat Product Security Team


More information about the net-dev mailing list