Asp.Net work process
ASP.NET runs within a process known as the ASP.NET worker process.
All ASP.NET functionality runs within the scope of this process.
A regular Web server contains only a single ASP.NET worker
process. This is different from both Web farms and Web gardens:
* A Web farm contains multiple ASP.NET worker processes.
Each server in the group of servers handles a separate
ASP.NET worker process.
* A Web garden contains multiple ASP.NET worker processes.
Each CPU in the SMP server handles a separate ASP.NET worker
Choosing an ASP.NET worker process
When a Web client connects to a Web farm or Web garden, one of the
multiple ASP.NET worker processes is selected to run the request.
* In a Web farm, Network Load Balancing determines the ASP.NET
worker process selected.
* In a Web garden, the ASP.NET worker process selected is
determined by ASP.NET.
State management with multiple ASP.NET worker processes
When moving from a scenario with a single ASP.NET worker process
(a normal Web server) to a scenario with multiple ASP.NET worker
processes (a Web farm or Web garden), complications with state
management are introduced.
Web pages are stateless, so a Web server must persist state
through other means. Typical means to manage state on the Web
server include Session State and the ASP.NET Cache.
Kk86kiran, if this helps please login to Mark As Answer. | Alert Moderator