I noticed that UnixDomainServerSocket returns useful information on a call to toString(), but it's friend UnixDomainSocket does not return useful information, it actually returns incorrect information:
Socket[unconnected]
More useful and correct output would be the path that was used to create the socket.
I have not tested the Win32NamedPipeSocket but I suspect a similar issue would occur.
I noticed that UnixDomainServerSocket returns useful information on a call to toString(), but it's friend UnixDomainSocket does not return useful information, it actually returns incorrect information: Socket[unconnected]
More useful and correct output would be the path that was used to create the socket.
I have not tested the Win32NamedPipeSocket but I suspect a similar issue would occur.