M
marian.edu
Guest
Caching otherwise dynamic content is most of the time not a good idea but depending on the specific content of one page you might decide to let the browser cache the content for one hour/day or more - there are http headers for that (see cache-control on Bronco’s link). If the content is actually dynamic but you still decide to cache the response then you might need to consider request path, query string, header information (cookies, accepted language, etc)… making a hash of all that is might take some extra processing and then you need to match that agains a potentially large (or growing) cache hash table. That need to be some extra cache management that handles expiration and clean-up of expired cache entries and if you’re on the appsrv and don’t use a database for that each agent will have it’s own cache hash-table so be prepare to throw in some extra RAM, on the other hand if you do use a database table for cache management you might have that I/O issue that was the reason you started to use cache come back and hunt you. Better just see why do you need the cache in the first place, reading a few records it should not be too much of a penalty if the database is modelled/set-up correctly (you’ll probably have all those records in memory anyway or you should)… if you need to have transactions then take a closer look and see why do you need to have updates, using a cache will defeat the purpose of those transactions anyway. Marian Edu Acorn IT www.acorn-it.com www.akera.io +40 740 036 212
Continue reading...
Continue reading...