httpapplication instance doubt

  • Thread starter Thread starter sikander khan via .NET 247
  • Start date Start date
S

sikander khan via .NET 247

hello all !
i know that there exists one to one relationship between HttpApplication instance and a request. My doubt is that instance associated with that request until session times out. i mean lifetime here means session time or not.
 
an HttpApplication lifespan is the life of the appdomain assoicated with the
vdir, not session. its created when the appdomain is loaded (first hit to
site), and destroyed when the appdomain unloaded (application is recycled).

-- bruce (sqlwork.com)

sikander khan via .NET 247 said:
hello all !
i know that there exists one to one relationship between HttpApplication
Click to expand...
instance and a request. My doubt is that instance associated with that
request until session times out. i mean lifetime here means session time or
not.
 
HttpApplication does not have a one to one relation with request

you have One HttpApplication, One Cache, One Session per user (if you have
session state - web.config).
The Request object has a life time of individual requests where instance of
page class is created and the request is processed. The response object
again has a life time associated with delievery of processed request.
They are all bound togather by what is called Context.

http://msdn.microsoft.com/library/en-us/dnaspp/html/dngrfTheASPNETHTTPRuntime.asp?frame=true

http://msdn.microsoft.com/library/en-us/dnaspp/html/aspnet-pageobjectmodel.asp?frame=true



--

Regards,

Hermit Dave
(http://hdave.blogspot.com)
 
If we are talking about the HttpApplication class, like the class that
Global derives from in IDE generated global.asax files, then there are
*multiple* instances of this class. They are kept in a pool, and one
instance is pulled from the pool and associated with a request during
it's lifetime, then returns to the pool.

I have some details and references in my article here:
http://odetocode.com/Articles/89.aspx
 
Back
Top