ASP.NET MVC4与Web API构建REST服务

ASP.NET.MVC4

5星 · 超过95%的资源需积分: 10 29 浏览量更新于2024-07-25 收藏 1.61MB PDF 举报

"Apress.ASP.NET.MVC4.and.the.Web.API.Feb.2013" 本书深入探讨了ASP.NET MVC 4框架以及与其相关的Web API技术，旨在帮助读者构建一个从头到尾的REST服务。作者Jamie Kurtz通过一系列章节详细介绍了如何利用这些工具构建高效、可扩展的Web应用。在第一章"ASP.NET MVC作为服务框架"中，作者首先讨论了当前JavaScript和移动设备盛行的背景下，ASP.NET MVC框架的优势。它强调了框架在构建现代Web应用中的灵活性和模块化设计。接着，对Web API进行了简要介绍，这是ASP.NET框架的一部分，专门用于构建RESTful服务，使得与服务器的交互更加简单和直观。第二章"什么是RESTful？"中，作者阐述了从远程过程调用（RPC）到REST的转变，比较了XML-RPC和SOAP等早期的Web服务技术。他详细解释了URI（统一资源标识符）和资源的概念，以及HTTP方法（如GET、POST、PUT、DELETE）在REST架构中的重要性。此外，还介绍了HATEOAS（超媒体作为状态的引擎）原则，它增强了服务的发现性和自描述性，以及HTTP状态码在通信中的角色。第三章"设计示例REST API"中，以任务管理为例，讨论了如何定义资源类型，并引入了超媒体链接的概念。这一章详细说明了如何根据资源设计URI和相应的HTTP动词，从而创建符合RESTful原则的API设计。作者强调了模型化URI和HTTP方法对于提供清晰、一致的接口至关重要。 ASP.NET MVC 4是Microsoft开发的一个强大的Web应用程序框架，特别适合构建动态、数据驱动的网站。它允许开发者使用模型-视图-控制器（MVC）设计模式，分离业务逻辑、用户界面和数据层。Web API则进一步扩展了这个框架的功能，使其能够轻松创建支持HTTP协议的API，适合移动应用和Web服务之间的通信。通过本书，读者不仅可以学习到ASP.NET MVC 4的基本概念和技术，还能掌握如何设计和实现RESTful服务，这对于任何希望构建现代、跨平台Web应用的开发者来说都是宝贵的资源。

CHAPTER 1 N ASP.NET MVC AS A SERVICE FRAMEWORK

If you need to set up communication between two applications, whether they are

co-located or separated by thousands of miles, rest-assured WCF can do it. And if its

out-of-the-box features don’t suffice, WCF’s tremendous extensibility model provides

ample opportunity for plugging in just about anything you can think of.

And this is where we will take a bit of a left turn, off the evolutionary path of ever

greater capability and flexibility, and towards something simpler and more targeted at a

small set of specific scenarios.

In the Land of JavaScript and Mobile Devices

During much of the growth of the Internet over the past two-plus decades, web sites and

pages have relied on server-side code for anything but basic HTML manipulation. But

more recently, various AJAX-related tools and frameworks—including (but not limited to)

JavaScript, jQuery, HTML5, and some tricks with CSS—have given rise to the need for

services that are less about complex enterprise applications talking to each other and

more about web pages needing to get and push small amounts of data. In these cases,

communicating with a service over HTTP is pretty much a given, since the web sites

themselves are HTTP applications. Further, security options available from within a

browser are vastly simpler than those of an out-of-browser application, and thus support

for all of the various security-related SOAP standards is not required of the service.

In addition to simpler protocol and security needs, web pages typically communicate

with other applications and services using text-based messages rather than binary-formatted

messages. As such, a service needs only to support XML or JSON serialization.

Beyond web applications, today’s smartphones and tablets have created a huge

demand for services in support of small smart-client mobile applications. These services

are very similar in nature to those that support AJAX-enabled web sites. For example,

they typically communicate via HTTP; they send and receive small amounts of text-based

data; and their security models tend to take a minimalist approach in order to provide

a better user experience (i.e., they strive for less configuration and fewer headaches for

users). Also, the implementation of these services encourages more reuse across the

different mobile platforms.

In short, there is now a desire for a service framework that, out-of-the-box, provides

exactly what is needed for these simple text-based HTTP services. While WCF can be used

to create such services, it is definitely not configured that way by default. Unfortunately,

the added flexibility and configurability of WCF make it all too easy to mess something up.

And this is where the ASP.NET MVC Framework comes into the picture.

Advantages of Using the MVC Framework

Once you know that, under certain scenarios, you aren’t interested in many of the

capabilities of WCF, you can start thinking of a framework like ASP.NET MVC—with fewer

service-oriented bells and whistles—as being advantageous. In this section, you’ll look in

detail at a few of these.

CHAPTER 1 N ASP.NET MVC AS A SERVICE FRAMEWORK

Statelessness x

Network layering (with various firewalls and gateways in between x

client and server)

This book will cover REST principles sufficiently for you to build services using

ASP.NET MVC. However, if you’re interested, you can find several good books that

cover the full breadth of the REST architecture. You might also find it interesting to

read Chapter 5 of Fielding’s doctoral dissertation, where the idea of REST was first

conceived. You can find that chapter here:

http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm

Before moving on, let’s address a point that some may be thinking about: you

can indeed create REST services with WCF. Looking around the Internet, you can

certainly find arguments on both sides of the MVC versus WCF debate (for building

RESTful services). Since this is a book on how to build services with MVC and the

Web API, let’s skip that debate altogether.

Abstraction with Routes

Somewhat similar to service interfaces and their implementations in WCF, routes give

the MVC service developer a layer of abstraction between what the callers see and the

underlying implementation. In other words, you can map any URL to any controller

method. When the API signature (i.e., the REST URL) isn’t hard-wired to a particular

interface, class, or .svc file, you are free to update your implementation of that API

method, as long as the URL specification for that method remains valid.

One classic example of using URLs to handle changing implementations is in the

case of service versioning. By creating a new route with a “v2” (or similar) embedded

in the URL, you can create an arbitrary mapping between an implementation and a

versioning scheme or set of versions that doesn’t exist until sometime later. Thus, you can

take a set of controllers (and their methods) and decide a year from now that they will be

part of the v2 API.

Controller Activation Is, Well, Very Nice

Whether the subject is the older XML Web Services (a.k.a. ASMX services), WCF, or

services with ASP.NET MVC, the concept of service activation is present. Essentially, since

by-and-large all calls to a service are new requests, the ASP.NET or WCF runtime activates

a new instance of the service class for each request. This is similar to object instantiation

in OO-speak. Note that service activation is a little more involved than simply having the

application code create a new object; this book will touch on this topic in more depth in

later chapters.

ASP.NET MVC provides a simple mechanism for pre- and post-processing called

action filters. These filters are essentially classes that contain a few methods allowing

you to run some code before and after the controller methods are invoked. These action

剩余139页未读，继续阅读

flyingWithJava

粉丝: 0
资源: 6

ASP.NET MVC4与Web API构建REST服务

最新资源