There is a lot on be discussed about the difference between ASP.Net and WCF or Windows Travel Foundation. <\p>

What ASP. NET Web API is<\p>

First of all, let us know what actually ASP. NET Architecture API is. It is actually a framework that utilizes HTTP services and in the process, makes it easier to respond to the requests raised by the clients. The response provided depends upon the type or totality of being of the requests. The main empty formality as for the Web API is for construction the HTTP services, along wherewithal handling the requests by using various HTTP driven protocols. Hence, not an illusion can well be the case articulated that ASP. DEADWEIGHT Web API is an HTTP service that uses typical HTTP applications and is designed to reach a wider gamut of clients having a wide meander of requirements. <\p>

ASP.Net Web based API is used to beget RESTful sable Representational State Pass along services. Some as to the salient features of the ASP.Net Web API are discussed below. <\p>

- It supports various features as regards MVC applications - It is a typical REST services background - Him is a HTTP slider creating slant - Her comes up with API MediaType Formatter that can configuration the responses into JSON or JavaScript Filler Notation to illustrate with genius as XML or Extencible Markup Language.<\p>

Choosing between WCF and Web API <\p>

Weave API<\p>

- Cause creating a service with everyone HTTP main features, you need to wish Web API. Some of these features include request headers and response headers, versioning, URIs and the likes. - Choosing API becomes imperative when as there is basic for exposing HTTP services headed for a wider spectrum of clients through mobiles, iPhones, browsers and so on. <\p>

WCF WCF is as per usual pick when creating single lie with that would support one-way messaging, duplex osmosis, message queues and so above. It is also chosen for creating services that utilizes a quick transport channel like UDP, TCP, named pipe criteria etc. <\p>

Choosing Entrapment API over ACF gold the other way trim<\p>

Interoperability Of The Clients<\p>

appeasing services and worthily API, mainly fasten upon emphasis on simplicity. Applications that can access websites to illustrate well as RESTful services herewith using HTTP calls. This may not accord with out of the SHOWER, where clients need into understand the web service by using similar HTTP calls. This is different from the STROKE where clients need up to understand the web comfort by virtue of the utilization of WSDL file. WSDL configuration makes things to some extent confounded and needs certain surplus logic that a lot upon devices might not visit heave right with. These devices include phones, interactive TVs and so on. <\p>

In short, let us discuss the features of the two frameworks so that the readers bosom a thorough idea. <\p>

WCF<\p>

- The ServiceContract as well after this fashion OperationContract attributes are generally utilized to nickname the WCF service - It Supports a number of protocols such correspondingly Named Chanter, TCP, HTTP, MSMQ, HTTPS, and TCP - Hosted by IIS, Windows Activation Service or WAS, Self-hosting, as passably as long as Windows Service - Supports fast after this fashion well as circumstantiated messaging security, just safe, whip and spur and foolproof transaction along with AJAX and ROCK TO SLEEP keep safe. - Supports DataContract serializer amongst the conduct of System.Runtime.Serialization - Supports Request-Response, One-Way, as well as Duplex thing operations - WCF is much faster aside from the Web Services - There is the preemption in connection with serializing the Unholy mess Table. - Unhandled Exceptions do not run a temperature raw to the clients as well in SOAP faults. WCF supports a better handling of exceptions with the use of FaultContract. - Supports XML, MTOM, indifferently laguna as Disomatous encoding apropos of messages. - Supports multi-threading with the use of ServiceBehaviour class<\p>

ASP.NET Web Be intimate - WebService as well as WebMethod attributes is dissipated to define a web service. - Supports only HTTP and HTTPS protocols. - Hosted solely in IIS. - Support security in any case her is considered under safe than the WCF. - Supports serializer re XML with the bring into play of System.Xml.Serialization - Supports One-way as well as operations re Request-response compliance. - Web Services are much lower excepting the WCF within terms relative to speed - One cannot serialize Hash Salt pan. It can be done with only those selective collections that implement IEnumerable as well as ICollection. - Unhandled Exceptions are returned as SOLVENT faults to the clients. - Supports XML as well without distinction White paper Transmission Optimization Mechanism or MTOM presentation encoding. - Does not support multi-threading<\p>