alexanderzeitler.com - Microsoft Web API – the REST is done by WCF (Part 1)

Microsoft Web API – the REST is done by WCF (Part 1) | Alexander Zeitler

Alexanderzeitler.com Spined HTML

Microsoft Web API – the REST is washed-up by WCF (Part 1) | Alexander Zeitler Toggle navigation Home Feed Microsoft Web API – the REST is washed-up by WCF (Part 1) Written on April 15, 2011 Postings published on this series so far: Microsoft Web API -- the REST is washed-up by WCF (Part 1) -- this one REST using the WCF Web API -- Basics (Part2) REST using the WCF Web API -- refactoring to IoC style (Part 3) REST using the WCF Web API -- getting RESTful the BDD way (Part 4) REST using the WCF Web API -- getting increasingly RESTful responses (Part 5) REST using the WCF Web API -- Post it! (Part 6) SOA? (c) geek&poke When speaking of SOA today, many developers still think well-nigh Web Services (which in specimen of .NET are ASP.NET Web Services or Windows Communication Foundation, transiently WCF) handling SOAP using XML and other standards to enable Remote Procedure Calls (read: calling functions on remote computers). As remote computers may be part of foreign domains or plane misogynist on the internet the need for hallmark and passport came up fast and has been satisfied by introducing the WS-Security extension to SOAP.Flipsideneed of undertow has been to have reliable messaging which lead to flipside extension tabbed WS-Reliability. In order to be worldly-wise to describe schemas of SOAP messages WSDL had been introduced. As you can see, there is a unconfined effort to mart data between two endpoints on the network. And plane worse: the list of extensions and format definitions is by far not complete, not to mention the problems welling in the wild. And now: the REST Despite having all these extensions you don't finger sophisticated nor productive when using SOAP and I would state that SOA has not infiltrated IT merchantry as buzzword-bingo scene wants to make us believe. On the other hand, the internet grows furious day by day while reaching into all areas of our live. Internet wouldn't be that successful if it where slow, unreliable and nonflexible to use and manage. Internet as most users know it using the browser of their nomination is based on the HTTP protocol which carries out the functions of the web based on operations stuff part of the HTTP specification. Anyone stuff familiar with web minutiae should know HTTP verbs (also tabbed "methods") like GET or POST. But there are increasingly verbs underneath them like the lesser known PUT or DELETE. Furthermore HTTP uses so tabbed Status Codes which tell the browser (e.g. with value 200 for "ok") and sometimes moreover the user directly (e.g. 404 for "Page not found") well-nigh the state of the current request stuff handled. Based on these and some other elements of the HTTP specification in 2000 Roy Fielding wrote his dissertation where he worked a new tracery for distributed applications using web technologies: Representational State Transfer, transiently REST. I want to point out that by no ways REST based architectures must be used in web applications only. They just re-use technologies stuff ripened for the web. There's a URI for That The part-way of a REST based tracery are resources which can be accessed by an unambiguous URI like: http://mybookstore.com/book/RESTInPractice Hence the typesetting "REST in Practice" is accessibly by every vendee (as the specimen may be without authentication) when knowing this URI. In a REST tracery a list of all books could be found here: http://mybookstore.com/books/ At this time we don't know which format will be returned calling both URIs nor do we know which HTTP method to use. But in the definition of REST architectures there's a well-spoken concept of this: When getting data from a resource you should unchangingly use HTTP GET. This leads to the requirement that by no ways the underlying data should be modified by this request so that this operation could be repeated wrong-headed and unchangingly returns the same data (unless it will be modified by other methods stuff designated for doing that). The format the tabbed method will return can be chosen by the vendee itself (as long as the resource provides multiple formats). However, formats are not requested by accessing http://mybookstore.com/book/RESTInPractice/PDF as one may suppose. It's workaday by setting the HTTP header instead. To request the PDF of the same typesetting by the once known URI, the accept-type in the HTTP header is set to "application/pdf". The URI of the typesetting remains the same: http://mybookstore.com/book/RESTInPractice The header is evaluated by the server and if the PDF of the typesetting is available, the resource delivers it in the response. The fact that the PDF of the typesetting is not misogynist can moreover be indicated using HTTP: By setting the status lawmaking in the HTTP header of our response to (e.g. 404 for the latter case) practically every state of a resource, request or at least the well-constructed server hosting the resource can be represented. Further details and sample implementations for .NET and JAVA based REST services and clients can be found in the "REST in Practice" book, which I would recommend to everyone playing virtually with REST. Microsoft and REST Of undertow there is a Microosft solution for REST based architectures. A few years ago Microsoft released the WCF Starter Kit. However I don't see it in the hall of fame of Microsoft products. As REST based architectures wilt increasingly and increasingly important nowadays and of undertow .NET developers moreover need to implement or at least use it, a few month ago Microsoft has started a new project tabbed "WCF Web API" to ease implementing REST using WCF both on server and vendee side - which I find has wilt a really good implementation until now. The latest shit are misogynist at http://wcf.codeplex.com. Glenn Block, the team lead of the new project has washed-up a Session at Mix 2011 priming tabbed "WCF Web APIs: "There's a URI for That" presenting the latest shit and samples. Since using the WCF Web API for a while now, I'll publish a series of blog posts on the WCF Web API here in the next days. These will not only imbricate the Web API itself but moreover testing it using the BDD framework machine.specifications/machine.fakes and wiring things up using the LightCore IoC container. Furthermore I will explain things like usage of HTTP methods like PUT and DELETE and will show off advantages of REST based architectures stuff implemented using WCF Web API. Postings published on this series so far: Microsoft Web API -- the REST is washed-up by WCF (Part 1) -- this one REST using the WCF Web API -- Basics (Part2) REST using the WCF Web API -- refactoring to IoC style (Part 3) REST using the WCF Web API -- getting RESTful the BDD way (Part 4) REST using the WCF Web API -- getting increasingly RESTful responses (Part 5) REST using the WCF Web API -- Post it! (Part 6) .aspx&bgcolor=3169AD&fgcolor=FFFFFF&border=000000&cbgcolor=D4E1ED&cfgcolor=000000) Please enable JavaScript to view the comments powered by Disqus. Copyright © Alexander Zeitler 2003 - 2016 | Impressum