Last post Jun 13, 2011 10:51 AM by atconway
Jun 10, 2011 06:15 AM|muralithangaraj|LINK
I have few doubts in application pool and application domain and differences of them. I have listed my understanding below, please let me know whether my understanding is correct or not. Also, please let me know where can i get good reference to know detailed
knowlege about Application pool and Application domain.
An application pool is a container to execute one or more applications/virtual directories, which means for a single application pool, one or more than one websites can be mapped. In a application pool, more than one worker processor can exists. if each
website in application pool is mapped to individual worker process, and if any issues occurs in one worker process, only that worker process will stored and restart, the other process will still run.
Application domain is mapped to individual worker process, that is w3wp.exe. but, there can be more than one application domain mapped to a single worker process (w3wp.exe).
Jun 10, 2011 06:36 AM|devensawant|LINK
Take a look at following links
Jun 13, 2011 10:51 AM|atconway|LINK
I have few doubts in application pool and application domain and differences of them.
A single application pool in IIS represents a single w3wp.exe process. Having multiple w3wp.exe process within a single app pool on a single server is called a 'Web Garden' (not the same as a 'Web Farm' which is multiple servers serving up the same site).
The main purpose for having multiple app pools is for application isolation by having distinct differences in Framework versions (i.e. one on .NET 2.0 and one on .NET 4.0), differing managed pipelines, differing identities run under, etc.
'Application Domain' is the process of separating applications into their own process so code run in another app does not affect another, and is isolated from other applications. This happens naturally in IIS when setting up separate web sites. 1 website
is not effected by code running on another website on that same server. There is no need to set up separate application pools for each website. Even a single IIS worker process will handle process isolation. You might be concerned about some things that are
automatically handled for you and are not a problem because IIS takes care of it for you.
Typically the biggest misunderstanding is between a Web Garden and a Web Farm. Or when to create separate application pools within IIS. If you would like to read further, check out the following (2) links:
Configuring Web Gardens with IIS 6.0 (IIS 6.0):
However, this is really pushing over to the IIS side of things more than .NET or ASP.NET, so you might want to also try re-posting to the IIS forums for some more detailed or *expert* help:
Hope this helps!