Kbase P101873: Poor performance of ASP.Net application uses DataGrid to allow the user to edit data
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
07/03/2005 |
|
Status: Unverified
FACT(s) (Environment):
OpenEdge 10.x
SYMPTOM(s):
ASP.Net application uses DataGrid to allow the user to edit data
When the user clicks the edit button for a given row the DataGrid will not go into edit mode unless you refetch the data from the AppServer and do a Merge() of the new data with the old data
Having to go back to the AppServer to re-fetch the data causes slow performance
CAUSE:
In ASP.Net when the edit button is clicked on the DataGrid the web page is posted back to the web server. This posting process, however, does not pick up where you previously left off. A new thread is created to handle the request and this means that all variables will be newly created (i.e. the DataSet which contained the data to which the DataGrid was bound must be rebuilt)
FIX:
Implement caching within ASP.Net