Support WCF via NamedPipes (and maybe UnixDomainSockets)
Opened this issue · 2 comments
Background
The in the 1.2 and 1.3 Launchers we support WCF (SOAP) over NamedPipes.
Since newer dotnet versions don't support WCF natively we use CoreWCF in the Launcher 2.0 which up until version 1.4 did not support NamedPipes.
Some of our users like to use NamedPipes instead of http to not have to open any ports on their machines.
Feature
We should add support for WCF via NamedPipes on Windows when the url prefix is set to net.pipe:// like we do in the 1.3 launcher.
Since 1.5 CoreWCF also supports UnixDomainSockets so we should use that instead of NamedPipes on Linux and MacOS.
looks like it should be fairly easy to support it as well with the current implementation. 😄
Open Questions
Do we want to automatically use UnixDomainSockets when the url prefix is net.pipe:// or do we want to use a different url prefix.
Do we want to deprecate the net.pipe:// prefix and switch to something like ipc:// for both or
a new one for either (e.g. namedpipe:// and unixdomainsocket://)
1.4 is released by now the latest version is https://github.com/CoreWCF/CoreWCF/releases/tag/v1.5.1 👌
We could also think about supporting rest and grpc via NamedPipes and UnixDomainSockets.