5 ms·
> design your messages first and then figure out what the URLs should look like. This is exactly what WCF let me do though and I wasn't limited to using HTTP l
by WorldWideWayne 11y ago
> design your messages first and then figure out what the URLs should look like.
This is exactly what WCF let me do though and I wasn't limited to using HTTP like the others you listed. I was able to use a full duplex binary tcp channel instead.
- judemelancon 11y agoI thought WCF was more hassle than it was worth. Then I got a massive performance boost from switching to the TCP transport with a quick configuration change ...and had fallback to HTTP after writing a few lines of code. Making the transport orthogonal to other concerns is a big win.
- sleepersmith 11y agoRofl. Good luck with that. 99% of the people don't even know wtf's WSHttpBinding.
- judemelancon 11y agoThis wasn't for a public API. It's employee-use-only business stuff; both client and server are bespoke.