Datasheet

Figure 1-2
Configurability
Another and more visible change is the integration of IIS configuration into the same process used for
configuring ASP.NET applications. Gone are the IIS registry settings, and the metabase that has been the
repository of IIS configurations in previous versions has been replaced by XML-based configuration files
that store both IIS and ASP.NET settings. This integration not only erases the line between ASP.NET
applications and the application server on which they run, but it also allows for better configurability
and easier deployment of both sites and applications. It also makes deployment across multiple systems
in web farms more straightforward and allows for extensibility of the configurations. IIS 7.0 introduces
the concept of shared configuration, wherein multiple web servers can point to the same physical file for
configuration, making deploying configuration changes to web farms nearly instantaneous.
IIS 7.0 now stores settings in a new applicationHost.config file. Additionally, IIS 7.0 configuration
options for individual websites or web applications can be stored in web.config files alongside ASP.NET
settings, in a new system.webServer section.
Browser
Begin Request
Authenticate Request
Authorize Request
Resolve Cache
Map Handler
Acquire State
Trace.exd Static File ISAPI.aspx
Pre-execute Handler
Execute Handler
Release Request State
Update Request Cache
End Session
Log Response
End Request
HTTP.SYS
11
Chapter 1: Background on IIS and New Features in IIS 7.0
97823c01.qxd:WroxPro 2/4/08 6:47 PM Page 11