Hello John, I have several questions regarding caching? 1./ Is it correct that whenever the caching in memory is no more available the caching from the disk will be used? I mean, why store it in 2 places if there will be just only one location to request it from, that would make no sense, right? Can you explain? 2./ In hosted environments it is possible to reset the app pool manually and automatically too many times by the provider. I suppose the memory cache is lost by then, right? 3./ Suppose the app. pool is frequently being reset and the cache is gone then. Wouldn't it be better to set the cache e.g. to 10 min. instead of 4 hours? I mean this way you can be quite sure that there will be a cached page when some one visits the website. Or does pageblaster have some solution for this? Like e.g. generating the page to be cached everytime the app pool is being reset? 4./ Last but not least. You mention that the module caching settings should be set to memory. I am using this setting for a while now. But suppose that in a hosted environement the available cache for each running website is just +/- 100 MB or less and that the app pool is being reset frequently. Would then caching the modules to disk be a better option? Like to know your opinion. Regards, Paco |