Web Servers and there Scurity
Reply
![]() |
|
From:
![]() chaitus
|
In earlier post i had discussed about IIS 5.0 Architecture as it helps us in understanding the architecture of IIS 6.0 which is the latest version available to us know. So today lets go into the architecture of IIS 6.0 to understand the compelling features provided by IIS 6.0 that contribute to the increase in scalability, reliability, and manageability.<o:p></o:p> IIS 6.0 is not that was built on the earlier version, but it has been totally re-designed with a new request processing architecture that has the benefits of high isolation without incurring the out-of-process cost which we discussed earlier, as well as much higher levels of reliability and scalability. You can split the main components of IIS 6.0 into the following two broad categories from the picture above.<o:p></o:p> - HTTP.SYS�HTTP.SYS is what which works in kernel-mode, it is also called as HTTP listener because it listens for incoming requests and queues those requests up on the appropriate queue. And each of this request will be serviced by one application pool. And an application pool in IIS 6.0 can contain one or more applications. Another important thing to note is that no third-party code i.e no other code can run in HTTP.SYS, improving the stability of the Web server. <o:p></o:p>
<o:p> </o:p> - WAS (Web Administration Service)�WAS is a user-mode configuration and process manager. The Web Administration Service component performs the following two operations: Configuration and Process Management. Again, no third party is allowed here. When the Web server is first initialized, the WAS configures HTTP.SYS and the application pools.
<o:p> </o:p> - Application Pool�Application pools are used to manage a set of Web sites and applications. Each application pool corresponds to one request queue within HTTP.sys which we discussed above and the one or more Windows processes that process these requests. One of the most important feature of IIS 6.0 is that it can support up to 2,000 application pools per server, and there can be multiple application pools operating at the same time. And these Application pools are separated from other application pools by Windows Server 2003 process boundaries. Therefore, an application in one application pool is not affected by applications in other application pools, and an application request cannot be routed to another application pool while being serviced by the current application pool. Applications can easily be assigned to another application pool while the server is running.
From, Shiva Chaitanya , Student Champ, Aurora's Engg College. |
|
View other groups in this category.
![]() |
To stop getting this e-mail, or change how often it arrives, go to your E-mail Settings.
Need help? If you've forgotten your password, please go to Passport Member Services.
For other questions or feedback, go to our Contact Us page.
If you do not want to receive future e-mail from this MSN group, or if you received this message by mistake, please click the "Remove" link below. On the pre-addressed e-mail message that opens, simply click "Send". Your e-mail address will be deleted from this group's mailing list.
Remove my e-mail address from dotNET User Group Hyd.
|
|
- Re: Web Servers and there Scurity chaitus
-