Web content cache types
Basic web content caching
The first time a web page is rendered by the WCM application, it is stored in a cache. Users then access this page from the cache until it expires. Only then is the web page rendered afresh. The main benefit of this scenario is improved performance. Basic caching should only be used on static content that does not require "real-time" access.
Advanced web content caching
Advanced caching can cache pages based on different user profiles.
Cache parameters in connect tags and URL requests can be used to override server's default advanced web content caching settings allowing you to set custom cache settings for individual web pages or components.
Type Details Site Same as the basic web content cache except that cache parameters in connect tags and URL requests can be used to override server's default advanced web content caching settings. Session A copy of each Web page a user visits is stored in the session cache. The User accesses the cached version of a web page until they start a new session, or until the cached web page is expired from the cache. User A copy of each Web page a user visits is stored in the user cache. The user accesses the cached version of a web page until the cached web page is expired from the cache. Secured Used on sites where the item security features are used to grant different users access to different Web pages and components based on the groups they belong to. Personalized Cache web pages of users who have the same "personalization profile". Users who have selected the same personalization categories and keywords, and who belong to the same group, share a single cache.
Default web content caching versus custom caching
Cache parameters in connect tags and URL requests can be used to override server's default advanced web content caching settings allowing you to set custom cache settings for individual web pages or components.In most cases, basic, site and session caching would only be used as server's default web content cache. User, secured and personalized caching would mostly be used when using custom caching in connect tags and URL requests.
If basic caching is used as default web content cache, custom caching cannot be used.
Cache comparisons
Function Basic caching Advanced caching Memory usage per item: Medium High Performance improvement: Very High High Custom caching available: No Yes Connect tag processing: No Yes Web Content Viewer Portlet: No Yes
Caching components
Web content caching can sometimes be used with Personalization components but will depend on the conditions set in the personalization rule, or the resources used to determine the rule results. Cache testing will be required to determine if the content returned by personalization component can be cached using web content caching.
Parent
Caching options