IIS 6.0 introduces a working process isolation mode that can run all web applications in an isolation environment. When running IIS in a working process isolation mode, the application can be configured to run in a separate application pool. Each application pool logically represents a configurable working process and links to applications in the pool. The working process runs independently of each other; they may fail, but they don't affect other work processes. Application pool protects the application from the work process that supports other application pools. This way, you can avoid the application of each other.
In the working process isolation mode, Hypertext Transfer Protocol (HTTP) requests directly route the kernel application pool queue that serves configured applications. Serving the working process of the application pool will pull the request directly from the queue to avoid the overhead of the process switching. To further protect WWW services, IIS 6.0 will isolate key web publishing service components such as HTTP protocol stacks and WWW services, avoiding its influence of third-party codes that are running in the working process. The HTTP protocol stack accepts the WWW service request and discharges it into the queue. The HTTP protocol stack continues to process the request when the working process is in an abnormal state and therefore interrupts the request. At the same time, the WWW service will detect abnormal working processes and turn it off. If the new work process is required to serve the request, the WWW service starts a new work process to get the request in the queue from the HTTP protocol stack. Even if the working process fails, the WWW service will continue to process requests and protect users from missing services. Open Internet Information Services (IIS) Manager, expand the server, right click on the application pool, select the properties. The process isolation is set according to your own system environment in the pop-up dialog box. Figure:
(Figure)
Since the system environment is diversified, it is difficult to have a standard, so please refer to Windows 2003 help.
