CHAPTER 1 ■ ASP.NET MVC AS A SERVICE FRAMEWORK
2
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.
- 1
- 2
- 3
- 4
- 5
前往页