Windows Server 应用程式相容性.ppt

IIS 6 monolithic For example, if you don’t want to use Digest Authenticaiton, you can clear the checkbox, but the code is still loaded in memory. It’s not used, but is still present. ASP.net is invoked when file extension is called and loaded into W3WP on demand. This is late in the IIS 6 request processing pipeline as several key events have already occurred including authentication. And how do you have functionality? You have to use ISAPI filters to handlers. While there performed well, you have to work within the contraints of ISAPI. IIS 7 takes the monolithic features of IIS 6 and breaks them into approx 40 modules. These modules register for events in the request processing pipeline such as the Authentication, Execute handler, or the send Response event. Since IIS 7 can preload .NET framework into the worker process, native and managed code modules can both service the request pipeline . ****************************************************************************************************** Script In this slide you can see that in IIS 6, ASP.net is loaded as an ISAPI application by the ISAPI handler. Inside the IIS 6 pipeline there is Authentication but there is also Authentication in ASP.net. ASP.net has it’s own handler mapping as does IIS 6. IIS 6 has it’s own error message and caching systems and ASP.net has these features as well, but they operate differently. This duplication of effort leads to confusion about which component is going to handle the various actions and leads to articles specifically written to help people understand how these things are related. ****************************************************************************************************** Script In IIS 7, the ASP.NET capabilities are moved into the IIS 7 core pipeline. This makes these features available to all requests, not just those bound for a .NET application. So if you want to use Forms authentication for a PHP website, go ahead! This also allows you to quickly