|
 |
aspx thread: ASP.NET Postback
Message #1 by "Garland Frye" <gfrye@s...> on Thu, 6 Dec 2001 14:33:28 -0600
|
|
I have a question regarding postbacks, any help would be greatly
appreciated...
Does a new object of the your webform class instantiate each time you post
back to the server, or refresh the page?
Thank you,
Garland R. Frye
Message #2 by "David DuVarney" <David.DuVarney@n...> on Thu, 6 Dec 2001 12:46:51 -0800
|
|
There is an article in the Beta 2 MSDN library that describes postback
processing(use these words to find it. It is categorized as a C#
concept).
The article does not explicitly say that the object instance is
destroyed, but I would assume that that is the case.
There are two things ASP.NET can do to improve performance in this
scenario. One is use the ASP.NET cache. Page results can be stored
there for a specific duration. Or (possibly), ASP.NET might take
advantage of COM+ object pooling.
Try to find the article. It contains some really good information.
Dave
link from VS.NET Beta 2:
ms-help://MS.VSCC/MS.MSDNVS/vbcon/html/vbconWebFormsPageProcessingStages
.htm
-----Original Message-----
From: Garland Frye [mailto:gfrye@s...]
Sent: Thursday, December 06, 2001 12:33 PM
To: ASP+
Subject: [aspx] ASP.NET Postback
I have a question regarding postbacks, any help would be greatly
appreciated...
Does a new object of the your webform class instantiate each time you
post
back to the server, or refresh the page?
Thank you,
Garland R. Frye
Message #3 by "Garland Frye" <gfrye@s...> on Thu, 6 Dec 2001 15:23:31 -0600
|
|
Thanks, I'll make sure I read that article
Garland
"David DuVarney" <David.DuVarney@n...> wrote in message
news:126742@a...
There is an article in the Beta 2 MSDN library that describes postback
processing(use these words to find it. It is categorized as a C#
concept).
The article does not explicitly say that the object instance is
destroyed, but I would assume that that is the case.
There are two things ASP.NET can do to improve performance in this
scenario. One is use the ASP.NET cache. Page results can be stored
there for a specific duration. Or (possibly), ASP.NET might take
advantage of COM+ object pooling.
Try to find the article. It contains some really good information.
Dave
link from VS.NET Beta 2:
ms-help://MS.VSCC/MS.MSDNVS/vbcon/html/vbconWebFormsPageProcessingStages
.htm
-----Original Message-----
From: Garland Frye [mailto:gfrye@s...]
Sent: Thursday, December 06, 2001 12:33 PM
To: ASP+
Subject: [aspx] ASP.NET Postback
I have a question regarding postbacks, any help would be greatly
appreciated...
Does a new object of the your webform class instantiate each time you
post
back to the server, or refresh the page?
Thank you,
Garland R. Frye
Message #4 by "Garland Frye" <gfrye@s...> on Thu, 6 Dec 2001 16:40:05 -0600
|
|
So I read the article, I realize the output to the browser gets rendered,
and destroyed with each round trip to the browser, my problem is specific,
If I have a dataSet declared at the Class("Page") level, what happens to
that dataSet when the client posts back, does that Class("Page") get
reinstantiated... In which case I would lose state for my dataSet, or does
the state for the class persist? The fact that you can check
"Page.IsPostBack" property tells me that state for the class persists???
Everyone feel free to comment!!!
Thanks,
Garland R. Frye
"David DuVarney" <David.DuVarney@n...> wrote in message
news:126742@a...
There is an article in the Beta 2 MSDN library that describes postback
processing(use these words to find it. It is categorized as a C#
concept).
The article does not explicitly say that the object instance is
destroyed, but I would assume that that is the case.
There are two things ASP.NET can do to improve performance in this
scenario. One is use the ASP.NET cache. Page results can be stored
there for a specific duration. Or (possibly), ASP.NET might take
advantage of COM+ object pooling.
Try to find the article. It contains some really good information.
Dave
link from VS.NET Beta 2:
ms-help://MS.VSCC/MS.MSDNVS/vbcon/html/vbconWebFormsPageProcessingStages
.htm
-----Original Message-----
From: Garland Frye [mailto:gfrye@s...]
Sent: Thursday, December 06, 2001 12:33 PM
To: ASP+
Subject: [aspx] ASP.NET Postback
I have a question regarding postbacks, any help would be greatly
appreciated...
Does a new object of the your webform class instantiate each time you
post
back to the server, or refresh the page?
Thank you,
Garland R. Frye
Message #5 by "Mark A. Struck" <mstruck@s...> on Thu, 6 Dec 2001 17:25:21 -0600
|
|
This is a multi-part message in MIME format.
------_=_NextPart_001_01C17EAD.46299D40
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Garland,
State is not maintained from page hit to page hit except for server-side
controls, where their state is stored in ViewState. I'm pretty sure that
Microsoft stores the property IsPostBack in ViewState also. If you
don't want to keep reinstantiating the dataset then I would advise
exporting the results(unless it is a large dataset) in XML and store it
in either the ViewState or in a session variable. This way every time
the form posts back you can repopulate your dataset from the XML instead
of making a call to the server. hope this helps
Mark
-----Original Message-----
From: Garland Frye [mailto:gfrye@s...]
Sent: Thursday, December 06, 2001 4:40 PM
To: ASP+
Subject: [aspx] Re: ASP.NET Postback
So I read the article, I realize the output to the browser gets
rendered,
and destroyed with each round trip to the browser, my problem is
specific,
If I have a dataSet declared at the Class("Page") level, what happens to
that dataSet when the client posts back, does that Class("Page") get
reinstantiated... In which case I would lose state for my dataSet, or
does
the state for the class persist? The fact that you can check
"Page.IsPostBack" property tells me that state for the class persists???
Everyone feel free to comment!!!
Thanks,
Garland R. Frye
"David DuVarney" <David.DuVarney@n...> wrote in message
news:126742@a...
There is an article in the Beta 2 MSDN library that describes postback
processing(use these words to find it. It is categorized as a C#
concept).
The article does not explicitly say that the object instance is
destroyed, but I would assume that that is the case.
There are two things ASP.NET can do to improve performance in this
scenario. One is use the ASP.NET cache. Page results can be stored
there for a specific duration. Or (possibly), ASP.NET might take
advantage of COM+ object pooling.
Try to find the article. It contains some really good information.
Dave
link from VS.NET Beta 2:
ms-help://MS.VSCC/MS.MSDNVS/vbcon/html/vbconWebFormsPageProcessingStages
.htm
-----Original Message-----
From: Garland Frye [mailto:gfrye@s...]
Sent: Thursday, December 06, 2001 12:33 PM
To: ASP+
Subject: [aspx] ASP.NET Postback
I have a question regarding postbacks, any help would be greatly
appreciated...
Does a new object of the your webform class instantiate each time you
post
back to the server, or refresh the page?
Thank you,
Garland R. Frye
|
|
|
View Cart
