Hacker News new | ask | show | jobs
by algorithmsRcool 2467 days ago
I liked kinda liked it, but trying to unify HTTP, TCP, Pipes and MSMQ into a single framework was probably overly ambitious. WCF always felt very complicated with all sorts of sharp edges to me.
2 comments

WCF also originally supported peer-to-peer network topologies, discovery methods like PNRP (Microsoft's competitor standard to eventual "winner" Bonjour/mDNS), various versions of the SOAP metadata formats, and WS-* standards, etc.

It was definitely ambitious. When it worked it was sometimes magic, and when it didn't it was a giant mess to resolve.

[ETA: In one past life I made the mistake of trying to use WCF Peer-to-Peer for a project and I still have scars from that. :O]

It has a steep learning curve, true.

I personally like sharing `interface.cs` rather than what appears very similar `interface.proto` plus a bunch of tooling.

Ahh well, things go in circles I guess.