Confused about caching
-
In a thread [http://www.codeproject.com/lounge.asp?forumid=1159&fr=51#xx889552xx [^]] about hosting sites in the Lounge one of the participants said the following.
For example, the server would cache my .ASP pages (even though I had no cache system implemented). So my clients ended up seeing 2 days old pages, even after I updated the ASP/HTML code!
My confusion over this statement is that I thought caching was implemented on the client macine to lighten the server load. I can't see any benefit for the server tier to cache pages. Am I missing something here? Thanks all. Best, Jerry
The only way of discovering the limits of the possible is to venture a little past them into the impossible.--Arthur C. Clark
-
In a thread [http://www.codeproject.com/lounge.asp?forumid=1159&fr=51#xx889552xx [^]] about hosting sites in the Lounge one of the participants said the following.
For example, the server would cache my .ASP pages (even though I had no cache system implemented). So my clients ended up seeing 2 days old pages, even after I updated the ASP/HTML code!
My confusion over this statement is that I thought caching was implemented on the client macine to lighten the server load. I can't see any benefit for the server tier to cache pages. Am I missing something here? Thanks all. Best, Jerry
The only way of discovering the limits of the possible is to venture a little past them into the impossible.--Arthur C. Clark
In a dynamically generated page, there may be many calls to database etc that use up a lot of resources. If the data doesn't change that frequently, then it would be useful for the server to cache the results and return the cached content, especially where the requests are coming from different users. Hence the need for server side caching.
-
In a dynamically generated page, there may be many calls to database etc that use up a lot of resources. If the data doesn't change that frequently, then it would be useful for the server to cache the results and return the cached content, especially where the requests are coming from different users. Hence the need for server side caching.
ChrisAdams wrote: If the data doesn't change that frequently, then it would be useful for the server to cache the results and return the cached content, especially where the requests are coming from different users. Hence the need for server side caching. That much I understand, but in this instace the poster is claiming that his pages were being chached over a several day period by the Hosting service. From my limited experience that doesn't make sense so I though I'd query here and see if anyone else can makes sense of that kind of setup. I mean, at best, a 10, 20, or maybe even 30 minute cache might make sense, but not a 24 to 48 hours cache. Or, again am I showing my ignorance of design? Best, Jerry
The only way of discovering the limits of the possible is to venture a little past them into the impossible.--Arthur C. Clark
-
ChrisAdams wrote: If the data doesn't change that frequently, then it would be useful for the server to cache the results and return the cached content, especially where the requests are coming from different users. Hence the need for server side caching. That much I understand, but in this instace the poster is claiming that his pages were being chached over a several day period by the Hosting service. From my limited experience that doesn't make sense so I though I'd query here and see if anyone else can makes sense of that kind of setup. I mean, at best, a 10, 20, or maybe even 30 minute cache might make sense, but not a 24 to 48 hours cache. Or, again am I showing my ignorance of design? Best, Jerry
The only way of discovering the limits of the possible is to venture a little past them into the impossible.--Arthur C. Clark
It sounds a bit excessive, but if the hosting service really want to reduce the load on their servers then they might do it. Sounds like he needs to change to a different provider.