| Author: ChandraShekar Thota 19 Jul 2008 | Member Level: Diamond | Rating:  Points: 6 |
For faster execution of ASP.NET applications, that are primarily based to be hosted on IIS servers, the aspnet_wp.exe comes into picture. This file (aspnet_wp.exe) is actually the ASP.NET worker process. The worker process is introduced to actually share the load on the IIS, so that application domains and other services may be maintained by a single worker process.
The aspnet_wp.exe worker process is a part of the Microsoft ASP.NET framework, and it is responsible for most of the technical processes in the ASP.NET framework. There may be multiple instances of ASP.NET worker process running on IIS 6 (a process running as inetinfo.exe), depending on multiple application pools. The worker process handles all the requests passed to the ASP.NET framework, so we may say that its actually the main engine that handles all requests pertaining to ASPNET. For example, when a request for an .aspx page is recieved by the IIS server, the dll called aspnet_isapi.dll passes this request to the aspnet_wp.exe worker process
|
| Author: UltimateRengan 21 Jul 2008 | Member Level: Diamond | Rating: Points: 1 |
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 process.
more reference login to:-
http://msdn.microsoft.com/en-us/library/ms225480(VS.80).aspx
http://www.daniweb.com/forums/thread8640.html
http://www.codeproject.com/KB/aspnet/aspwp.aspx
|