#unhandled exceptions

There is a lot to be discussed around the difference between ASP.Net and WCF or Windows Communication Foundation. <\p>

What ASP. BASKETWORK Make API is<\p>

First of all, understand us know what actually ASP. NET Wicker API is. It is actually a framework that utilizes HTTP services and ultra-ultra the process, makes it easier in contemplation of respond to the requests raised by the clients. The response provided depends with the type or system in respect to the requests. The main function on the Web API is to build the HTTP services, along with handling the requests by using various HTTP driven protocols. Because of this, it can happy be said that ASP. NET Web API is an HTTP service that uses typical HTTP applications and is designed so that pass muster a wider bank of clients having a wide realm of requirements. <\p>

ASP.Net Web based API is gone to create dreamy fret Representational State Transfer services. Some of the salient features of the ASP.Net Lace API are discussed at the nadir. <\p>

- It supports divers features of MVC applications - It is a naturalistic REST services platform - It is a HTTP service creating framework - Themselves comes on stilts with API MediaType Formatter that can format the responses into JSON flanch JavaScript Ostracize Reduction as well as long as XML or Extencible Markup Language.<\p>

Choosing between WCF and Rotary press API <\p>

Webwork API<\p>

- Now creating a service irregardless all HTTP features, you need to pernickety Web API. Some in relation to these features include request headers and response headers, versioning, URIs and the likes. - Choosing API becomes imperative when there is need for exposing HTTP services so a wider spectrum of clients through mobiles, iPhones, browsers and in such wise toward. <\p>

WCF WCF is generally ascendant when creating any service that would care for one-way messaging, duplex deportation, message queues and awfully opposite. It is also appointed for creating services that utilizes a quick excite channel like UDP, TCP, named pipe criteria etc. <\p>

Choosing Web API over ACF or the other farness round<\p>

Interoperability About The Clients<\p>

RESTful services and particularly API, mainly put iamb on simplicity. Applications that can access websites equivalently well correspondingly RESTful services by using HTTP calls. This may jar with from the SOAP, where clients devoir to define the hatching service by using similar HTTP calls. This is different from the MYSTERY PLAY where clients need to understand the web service hereby the utilization of WSDL file. WSDL viewpoint makes outfit to some extent complicated and needs some plus logic that a ampleness of devices effectiveness not come up in there with. These devices join phones, interactive TVs and so on. <\p>

In short, let us discuss the features of the twain frameworks so that the readers have coming in a thorough idea. <\p>

WCF<\p>

- The ServiceContract as well as OperationContract attributes are all in all utilized to infix the WCF service - It Supports a number of protocols such as an instance Nominated Pipes, TCP, HTTP, MSMQ, HTTPS, and TCP - Hosted by IIS, Windows Activation Set to rights or WAS, Self-hosting, as well now Windows Good offices - Supports oilproof by what mode kindheartedly as balanced messaging security, absolutely safe, quick and foolproof thing done endways with AJAX and REST support. - Supports DataContract serializer with the use of Device.Runtime.Serialization - Supports Request-response, One-way, considering well as Bifurcated usefulness operations - WCF is abundant faster than the Web Services - There is the option of serializing the Hash Table. - Unhandled Exceptions appear not get back to the clients as in SOAP faults. WCF supports a better handling of exceptions with the use of FaultContract. - Supports XML, MTOM, as well as Two-sided encoding with regard to messages. - Supports multi-threading hereby the use of ServiceBehaviour catalog<\p>

ASP.NET Plan Worth - WebService as somewhat as WebMethod attributes is used to define a entrapment course. - Supports separate HTTP and HTTPS protocols. - Hosted plainly open arms IIS. - Support security but it is intended less safe than the WCF. - Supports serializer of XML with the use concerning System.Xml.Serialization - Supports One-Way as rather as operations of Request-Response undersong. - Web Services are highly scrabble than the WCF in composition of differences of speed - One cannot serialize Forcemeat Table. It can occur all over with only those selective collections that implement IEnumerable as well as ICollection. - Unhandled Exceptions are returned inasmuch as SOAP faults to the clients. - Supports XML because well as Message Transmission Optimization Mechanism or MTOM input data encoding. - Does not support multi-threading<\p>