I understand that updating every page, especially in "AjaxLand", calls my back-end / code-behind class from scratch ... This is a problem because my class (which is a member object in System. Web.UI. Page) contains a lot of data that it is from the database. So, now updating each page in AjaxLand causes me to make big DB calls, and not just to reuse the class object from memory. Any fix for this? This is where session variables come into play? Are session variables the only way to store an object in memory that is associated with a single-user and single-session instance?
You need ASP.Net caching .
In particular, data caching .
If your data is user-specific, then Session will be a way. Be careful if you have a web farm or web garden. In this case, you will need a session server or database for the session.
If your data is application tiers then Application Data Cache might be the way to go. Be careful if you have limited RAM and your data is huge. The cache may free up at the wrong time.
, . , , .
, Lazy Loading , .
MS ASP.NET. " ".
Ajax, , :
, , , Ajax , (.. /JavaScript ..), . , . , JavaScript DOM - . .
, , , - , . , , , (), , .
, , , . , , , , .