In .NET 4 there will be the Routing Service, which will serve to fill the gap between clients and services that previously existed in WCF. Great! But what are we really giving you beyond a simple proxy? Intermediaries can be chock full of features, and serve a whole variety of needs. Instead of first talking about features, I'm going to give a quick set (off the top of my head) of our priorities when we built the Routing Service.
So this is all well and good, but what did we actually build? :) What can the Routing Service do?
It turns out there four major capabilities that the Routing Service gives you:
We feel like each of these was necessary in order to deliver a solid generic message router in V1 (of course you may disagree, or think we left something out. If this is the case, I'd love to hear from you in the comments).
I'll cover each of these in more detail in future posts, but hopefully you've already got some ideas about how you could use these capabilities when you're writing your WCF applications.