Ok, Server Side Caching is not in 6.0, what's next...background and direction forward Kevin Lynch 9.Oct.02 10:25 AM Lotus Notes Domino Server 6.0All Platforms
The decision to remove server side caching of web pages in Domino 6 was based on a number of factors. First was our own internal testing which showed us that in typical usage scenarios, server side caching achieved little, if any, performance improvement due to factors such as browser side caching and the fact that only static content pages are eligible for server side caching. Second was the significant performance improvements made to underlying subsystems in Domino 6 (often times as a result of better caching within those subsystems). We felt that the improved performance in these subsystems from which page result were built would, to a certain extent, mitigate the performance lost in those atypical cases where server side caching of page results really did make a difference. Another factor that figured into this decision was the addition in Domino 6 of better internationalization support and the User Preferences feature, both of which increased the customization of content thereby reducing cachablity.
As for $CacheValid, I think that we underestimated the extent to which some of our customers relied on this feature. So in response to the pleas in this forum and elsewhere, we have decided that we will re-enable support for $CacheValid in a future maintenance release of Domino 6.0x. However, this support is being re-enabled for backward compatibility only and will not support new features in Domino 6. As a result, the use of either the improved internationalization support, or User Preferences, will impact the effectiveness of $CacheValid. More specifically, if these new features are enabled (this is the default) and a response contains any localizable field (time, date, currency, etc.) or any server resource strings from which more than one language can be chosen, then the response will not be cached, even if the form contains the $CacheValid field. You can disable these new features by setting "Store Web user preferences in cookies:=Disabled" and "Default regional locale:=Server locale" in the Web User Preferences section of the Domino Web Engine tab in the server record or web site document. With these settings, $CacheValid will have the same effectiveness as it did in R5 for all responses. Without these settings, some responses with $CacheValid may not be cached, depending upon if they contain localizable fields or resource strings.