J
John Kotuby
Hi guys,
I have finally added the AJAX extensions to my ASP.NET project in VS 2005
and VB. It was far simpler than I had anticipated, and I wondering why I
didn't use the Update Panel sooner.
Anyway, one of my pages has many controls and populates large DropDown lists
etc.
There are only 2 controls on that page using the update panel now
(listboxes) and a very small set of data needs to be transfered with each
asynchronous postback. The contents of the 2nd listbox is determined by the
user selection in the first listbox. So , I need to update only about 20 or
30 lines of data with each callback. This operation is taking a very long
time compared to a nearly identical operation on a much smaller page.
However, I have read that what happens on the server is an entire page
life-cycle process even with a callback (the server considers it a
postback?). So I am guessing that a whole bunch of things are going on that
I really don't need.
Other than using "If Not Page.IsPostback" to cut down on the server side
processing, is there any way to tell the server to just run a particular Sub
or Function during the callback?
I would like to stay away from web services if possible to avoid another
learning curve.
Point me to a resource if there is one that is directly related to my
particular concern.
Or are there any other suggestions?
TIA
I have finally added the AJAX extensions to my ASP.NET project in VS 2005
and VB. It was far simpler than I had anticipated, and I wondering why I
didn't use the Update Panel sooner.
Anyway, one of my pages has many controls and populates large DropDown lists
etc.
There are only 2 controls on that page using the update panel now
(listboxes) and a very small set of data needs to be transfered with each
asynchronous postback. The contents of the 2nd listbox is determined by the
user selection in the first listbox. So , I need to update only about 20 or
30 lines of data with each callback. This operation is taking a very long
time compared to a nearly identical operation on a much smaller page.
However, I have read that what happens on the server is an entire page
life-cycle process even with a callback (the server considers it a
postback?). So I am guessing that a whole bunch of things are going on that
I really don't need.
Other than using "If Not Page.IsPostback" to cut down on the server side
processing, is there any way to tell the server to just run a particular Sub
or Function during the callback?
I would like to stay away from web services if possible to avoid another
learning curve.
Point me to a resource if there is one that is directly related to my
particular concern.
Or are there any other suggestions?
TIA