Use Namedpipes and UnixDomainSockets for ProcessHostService communication #112
Labels
feature-request
New feature or request
planned-feature
A feature that was planned and committed to by the maintainers
Currently the
ProcessHostService
is binding its gRPC service to a port.Depending on the whole networkstack for this provides more than we need and can be error prone (two launchers cannot be started easily when using the same port).
Solution 1
Since we only have one way communication from the plebeians to the monarch we could use .NET AnonymousPipes for communication. The monarch creates the pipe server and passes the client handle string to the plebeians. We'd probably need to pass JSON messages between plebeian and monarch.
Solution 2
Continue to use gRPC but use unix domain sockets and named pipes.
The text was updated successfully, but these errors were encountered: