What is the lifespan of a Page object?

[=?Utf-8?B?RGF2aWQgVGhpZWxlbg==?=]

Hi;

When a Page object - the code-behind of an aspx page is created - what is
the lifespan of that created object? Is it tied to the session, the
request/response, or is it in a poll and reused for the next request/response
to that page from any session?

--
thanks - dave
david_at_windwa rd_dot_net
http://www.windwardreports.com

Cubicle Wars - http://www.windwardreports.com/film.htm

[Laurent Bugnion [MVP]]

Hi,

David Thielen wrote:

Hi;

When a Page object - the code-behind of an aspx page is created - what is
the lifespan of that created object? Is it tied to the session, the
request/response, or is it in a poll and reused for the next request/response
to that page from any session?

The Page object is created when the Request arrives, and is disposed
after the Response is sent. A new Page object is created for each Request.

This is pretty heavy, that's why lightweight custom handlers like ASHX
are sometimes preferrable for intense traffic.

HTH,
Laurent
--
Laurent Bugnion [MVP ASP.NET]
Software engineering, Blog: http://www.galasoft-LB.ch
PhotoAlbum: http://www.galasoft-LB.ch/pictures
Support children in Calcutta: http://www.calcutta-espoir.ch

[=?Utf-8?B?RGF2aWQgVGhpZWxlbg==?=]

That helps - boy that is heavy. I like java stateless session beans - it just
keeps a pool of them so no big hit once the site starts.

--
thanks - dave
david_at_windwa rd_dot_net
http://www.windwardreports.com

Cubicle Wars - http://www.windwardreports.com/film.htm


"Laurent Bugnion [MVP]" wrote:

Hi,

David Thielen wrote:

Hi;

When a Page object - the code-behind of an aspx page is created - what is
the lifespan of that created object? Is it tied to the session, the
request/response, or is it in a poll and reused for the next request/response
to that page from any session?

The Page object is created when the Request arrives, and is disposed
after the Response is sent. A new Page object is created for each Request.

This is pretty heavy, that's why lightweight custom handlers like ASHX
are sometimes preferrable for intense traffic.

HTH,
Laurent
--
Laurent Bugnion [MVP ASP.NET]
Software engineering, Blog: http://www.galasoft-LB.ch
PhotoAlbum: http://www.galasoft-LB.ch/pictures
Support children in Calcutta: http://www.calcutta-espoir.ch

[=?UTF-8?B?R8O2cmFuIEFuZGVyc3Nvbg==?=]

David Thielen wrote:

That helps - boy that is heavy. I like java stateless session beans - it just
keeps a pool of them so no big hit once the site starts.

Not so very heavy. If it really would have been that heavy, they would
have been pooled. For any regular web page it works just fine.

--
Göran Andersson
_____
http://www.guffa.com

[Steven Cheng[MSFT]]

Some additional info on this.

Hi Dave,

You can check the following MSDN reference:

#ASP.NET Application Life Cycle Overview
http://msdn2.microsoft.com/en-us/library/ms178473.aspx

And notice these two events:

Raise the PreRequestHandl erExecute event.

Raise the PostRequestHand lerExecute event.

Between these two events, the runtime pipeline will locate a proper
httphandler to process the request. For aspx page, the handler is just the
corresponding page class. Therefore the page's whole lifecycle can be
considered as a sub period of the application request's lifecycle.

Hope this helps further.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.