Closed
Description
Unix domain sockets have a convention that a leading @ in the socket name denotes an address in the abstract namespace. This doesn't seem to work in either client or server.
Example:
builder.AddListeningPort("unix:@foo", grpc::InsecureServerCredentials());
What should happen:
Server opens abstract unix domain socket with name 'foo'
What actually happens:
Server opens non-abstract unix domain socket with name '@foo' in current working directory
GRPC 0.11.1