IIS7 will ship with both Windows Vista and Windows Longhorn Server.
It’s obvious that Microsoft has put a lot of time and effort into this
release and you can expect IIS7 to be the platform of choice as soon as
people can get their servers upgraded. It includes a several new
functionalities with very rich integration with ASP.NET.
Feature 1: HttpModules and HttpHandlers can participate in all the requests i.e we can have a ASP.NET HttpModule for a JSP or PHP page even. Building HTTPmodules for authentication, authorization, logging, url-rewriting, auditing now will be very easy with .NET.
Feature 2: ASP.NET configuration can be integrated with IIS. IIS now uses the same web.config configuration model, which means you can have both configure ASP.NET and IIS in a single web.config file. You can now set things like default pages, IIS security, logging, etc within a web.config file and xcopy/ftp it to a server.
Feature 3: This has an integrated Admin UI tool that can manage both IIS and ASP.NET settings. Rich GUI supports settings for Membership, Roles and Profile providers. This tool also supports remote delegated admin over http — which means you can point the rich-client admin tool at a shared host server and manage your users/roles/profile settings remotely over http.
Feature 4:It provides better request auditing and error debugging. A new functionality called “Failed Request Event Buffering” (affectionately known as “FREB”) is introduced. This allows administrators to configure applications to automatically save request information anytime an error occurs during a request, or if a request takes longer than a specified amount of time to complete. This allows us to analyze what exactly happened during a request failure and what errors or exceptions have occurred. This can capture tracing messages generated within ASP.NET or within any component or class library that uses System.Diagnostics — which makes it much easier for developers and admins to instrument and analyze what is going on with systems at runtimes.
Feature 5: It provides better configuration APIs and command-line tools. In addition to new config and admin APIs, we now have a great command-line admin story that you can use to set/modify/retrieve all configuration information as well as manage the server (start/stop individual apps, lookup their health state, register new apps, refresh SSL certs, etc).
Feature 6: Modular Architecture
Unless you’ve been living under a rock somewhere for the past few years, you’ve heard about all the problems that IIS has had when it comes to security. In earlier versions of IIS, it was either installed or it wasn’t. If IIS was installed then all the features were installed. In an attempt to minimize potential vulnerability, in IIS 6, the majority of features were disabled by default, but they still got installed. This time around Microsoft has taken the next logical step. IIS7 is almost completely modular.
Feature 1: HttpModules and HttpHandlers can participate in all the requests i.e we can have a ASP.NET HttpModule for a JSP or PHP page even. Building HTTPmodules for authentication, authorization, logging, url-rewriting, auditing now will be very easy with .NET.
Feature 2: ASP.NET configuration can be integrated with IIS. IIS now uses the same web.config configuration model, which means you can have both configure ASP.NET and IIS in a single web.config file. You can now set things like default pages, IIS security, logging, etc within a web.config file and xcopy/ftp it to a server.
Feature 3: This has an integrated Admin UI tool that can manage both IIS and ASP.NET settings. Rich GUI supports settings for Membership, Roles and Profile providers. This tool also supports remote delegated admin over http — which means you can point the rich-client admin tool at a shared host server and manage your users/roles/profile settings remotely over http.
Feature 4:It provides better request auditing and error debugging. A new functionality called “Failed Request Event Buffering” (affectionately known as “FREB”) is introduced. This allows administrators to configure applications to automatically save request information anytime an error occurs during a request, or if a request takes longer than a specified amount of time to complete. This allows us to analyze what exactly happened during a request failure and what errors or exceptions have occurred. This can capture tracing messages generated within ASP.NET or within any component or class library that uses System.Diagnostics — which makes it much easier for developers and admins to instrument and analyze what is going on with systems at runtimes.
Feature 5: It provides better configuration APIs and command-line tools. In addition to new config and admin APIs, we now have a great command-line admin story that you can use to set/modify/retrieve all configuration information as well as manage the server (start/stop individual apps, lookup their health state, register new apps, refresh SSL certs, etc).
Feature 6: Modular Architecture
Unless you’ve been living under a rock somewhere for the past few years, you’ve heard about all the problems that IIS has had when it comes to security. In earlier versions of IIS, it was either installed or it wasn’t. If IIS was installed then all the features were installed. In an attempt to minimize potential vulnerability, in IIS 6, the majority of features were disabled by default, but they still got installed. This time around Microsoft has taken the next logical step. IIS7 is almost completely modular.
No comments:
Post a Comment