In the world of HTML5, mobile devices, and modern development techniques, HTTP has become the default option for building rich, scalable services. The ASP.NET Web API was designed from the ground up to meet the need of developers who want to build HTTP/RESTful services. The API provides an easy-to-use set of default options, while providing a deep extensbility infrastructure to meet the demands of any scenario using HTTP.
Table of content
Introduction
- Introduction
- What
- Why
- Is this REST?
- Versus WCF
- Demo – ASP.NET Web API Hello World
- More Details
- Assemblies
- Convention
- Model Binding
- Content negotiation
- Demo Two – HttpResponseMessage
- OData Query Syntax
- Configuration
- Hosting
- Security
- Summary
- Introduction
- REST
- URIs
- Implementing with ASP.NET Web API
- Demo: Convention
- ApiController
- Verbs to Attributes
- Demo: Configuration
- Content Negotiation
- Model Binding
- HTTP – Diving Deeper
- Summary
Building clients with the ASP.NET Web API.
- Introduction
- Why Another New Client Class for HTTP?
- HttpClient Model
- Using the HttpClient
- Demo: Twitter Search with HttpClient
- Media Types
- Demo: Posting a Video
- Other Client issues
- Per-request headers
- DelegatingHandler
- Security
- Summary
Hosting options with the ASP.NET Web API.
- Introduction
- HttpConfiguration
- The HttpConfiguration class
- Self-hosting
- Self-hosting choices
- Demo: self-hosting
- HttpSelfHostServer
- Demo: using ApiController in self-hosting
- Message Handler party trick
- Demo: HttpServer passed to HttpClient
- ASP.NET Hosting
- Demo: Modiying ASP.NET configuration
- Summary
Security
- Introduction
- What’s new for ASP.NET Web API Security
- Authentication
- Self Hosting Security
- Demo: Self-Hosting & Security
- OnConfigureBinding
- Summary
Extensibility
- Introduction
- Getting Started
- Formatters
- Demo: Formatters
- Filters
- Demo: Filter
- Message Handlers
- Demo: MessageHandler
- DelegatingHandler
Depositfiles.com
Letitbit.net
No comments:
Post a Comment