|
|
|||||||||
|
|||||||||
| |||||||||
|
|
|
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
#1
|
|||
|
|||
|
I found this article and it seems like a good idea to put data into Application variable that doesn't change often.
Caching records in memory I am new to ASP and MS Access, would like to know from you folks whether this is a good practice to, say displaying Categories and Country data of an e-commerce site using this method? Thanks ![]() |
|
#2
|
|||
|
|||
|
Certainly its a viable option. See this article as well. http://www.4guysfromrolla.com/webtech/111000-1.shtml
I would say that for pages where which may not be accessed as frequently, that there isn't much point to cache the data. But if you are talking about something like the front page to a website, then of course caching would make sense. And if you do as this article suggests and update the cache every fifteen minutes then at most your site will be fifteen minutes old. A small price to pay for what I think would be a large increase in performance. As long as you the data that you are caching can be 15 minutes old, I wouldn't want to cache say stock quotes or sports scores obviously |
|
#3
|
|||
|
|||
|
Thanks imbrokn.
I agree that all data can not be cached but in my case caching categories and country data could be cached in this manner. |
![]() |
| Viewing: Dev Shed Forums > Programming Languages - More > ASP Programming > Caching data to speed page response |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|