• ITVidya.com One Purpose...One Dream...One Vision..One Mision..Your Wealth Creation through Knowledge, Networking and Opportunity

asp

ASP.NET Application Request Cycle

ASP.NET is a powerful and flexible engine for processing web requests. It is a platform for building managed Web applications. The entire ASP.NET engine is completely built in managed code and all extensibility is provided via managed code extensions.

Application Request Cycle:

ASP.NET takes an incoming HTTP request and passes it through its internal pipeline to an endpoint where a code can be attached to process that request. This engine is separated completely from the web server. The HTTP Runtime is a component that can be hosted in applications outside IIS or on any server side application.

The entire ASP.NET engine is completely built in managed code and all of the extensibility functionality is provided via managed code extensions. With few limitations, ASP.NET can perform tasks that previously were the domain of ISAPI extensions and filters on IIS. ASP.NET interacts with IIS through an ISAPI extension that hosts .NET and ASP.NET runtime. ISAPI is a low level win32 API that provides the core extensions that hosts .NET and through it the ASP.NET runtime. ISAPI provides the core interface from the web server. ASP.NET uses the unmanaged ISAPI and provides the core interface from the web server. ASP.NET also uses the unmanaged ISAPI code to retrieve input and send output back to the client. The content that ISAPI provides is available via common objects like HttpRequest and HttpResponse that expose the unmanaged data as managed objects.

ASP.NET web request begins on the browser with a user typing in a URL and submitting a HTML form (a POST request) or an application making web method call to an ASP.NET based web service. The web server on the server side, Internet Information Server 5 or 6 picks up the request. The request goes through an ASP.NET application extension (eg: .aspx, asmx etc) that is registered and points at aspnet_isapi.dll. HttpHandlers are responsible for processing the request. Depending on the extension, ASP.NET routes the request to an appropriate handler that is responsible for picking up requests. HttpHandlers are mapped to point at the ASP.NET ISAPI extension in IIS, and configured in web.config to get routed to a specific HTTP Handler implementation. HttpHandler is a .NET class that handles a specific extension.

The worker processes ASPNET_WP.EXE in IIS5 and W3WP.EXE in IIS6 host the .NET runtime. The ISAPI DLL calls into small set of unmanaged interfaces via low level COM that eventually forward call to an instance subclass of the ISAPIRuntime class. The transfer of the ISAPI request into the HTTP Pipeline of ASP.NET uses a number of undocumented classes and interfaces and requires several factory method calls. The first entry point to the runtime is the undocumented ISAPIRuntime class which exposes the IISAPIRuntime interface via COM to a caller. Each Web Application runs in its own AppDomain with the caller holding a reference to an IISAPIRuntime interface that triggers the ASP.NET request processing.

 

Naukri IPO

After months of speculation and waiting Naukri.com finally and officially announced that it its going public . it has submited its IPO filing with sebi .
Althoug timing is a little odd but still this is really an exciting news for Internet Business in India . Sanjeev has proved that Internet business can make money and to be profitable you don’t really need to have an worldwide audience to serve . you can do it by serving the need to domestic customers also .