Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Persistence in WebParts
Message
Information générale
Forum:
ASP.NET
Catégorie:
Conception classe
Titre:
Persistence in WebParts
Versions des environnements
Environment:
C# 2.0
Database:
MS SQL Server
Divers
Thread ID:
01146511
Message ID:
01146511
Vues:
74
Hi all,

I'm creating some custom web parts that pull data from SQL Server and display the data via a DataGrid. What's the best approach for persisting the data retrieved from SQL so that the query doesn't have to be re-run every time the user clicks just about anything on the page? For example, if I have two web parts on the page, the user clicks on the header of a grid in one of them to sort on that column, both web parts are rebuilt completely (or at least, so it seems) so that the web part class is initialized and the data is pulled again.

How is this typically handled on the web in general? Control State? View State? Session Ojbects?

TIA,
Chad
_________________________________
There are 2 types of people in the world:
    Those who need closure
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform