Hacker News Reader

Comment by throwaway55554 | Hacker News Reader

I'm curious and don't see anything. But what about things like IPC? Is WCF available yet? Is there an abstraction for namedpipes for all the platforms?

View on HN

IPC is already supported. We have no plans to support WCF (as a server) on .NET Core.

What components of.NET Framework 4.8 will not be supported on the Windows version of.NET 5?

I suspect that WCF is mostly on its way out, but don’t quote me on that. There seems to have been little interest in continuing to support it.

I'm primarily a .NET developer - I haven't seen WCF used in a new project for maybe 10 years or so. It lost out to simpler, JSON-over-HTTP a long time ago, and good riddance!

Ok, but surely that's not used for IPC.

Nowadays many people do indeed use JSON over HTTP for IPC - it's the lifeblood of microservices.

More efficient protocols are also used of course, such as Cap'n Proto, Protocol Buffers etc.

Ok, I get if they're looking to scale and have them on multiple machines. But I tend to use namedpipes and/or shared memory because I need fast access between multiple services on the same machine. I don't need to scale.

You can use named pipes without WCF[0]. Sample here[1].

I've also used the IpcServiceFramework[2] before, and it worked a treat.

[0] https://github.com/dotnet/docs/blob/master/docs/standard/io/...

[1] https://github.com/GustavoHennig/PipePoc

[2] https://github.com/jacqueskang/IpcServiceFramework

Reply on news.ycombinator.com