Supporting Diverse Clients
At this point, we’ve demonstrated that ASP.NET Web API is an excellent platform on which to implement REST-based services. However, what if you found yourself in a situation where you had to support existing legacy (asmx-based or SOAP-based) clients? Or clients that required messages to be in XML format? Would that automatically eliminate ASP.NET Web API as a technology choice? Fortunately, the answer is no.
And that leads us to the subject of this chapter—namely, how to use ASP.NET Web API to simultaneously support legacy clients and extend reach to clients requiring various message formats. Along the way, ...