Web content cache types

Web content cache types

+

Search Tips | Advanced Search

This topic describes the types of caching used by IWWCM .

Basic web content caching

This is the simplest caching option. 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

There are two major differences between basic caching and advanced caching:

Advanced caching can cache pages based on different user profiles.

Cache parameters in connect tags and URL requests can be used to override the server's default advanced web content caching settings allowing one to set custom cache settings for individual web pages or components.

There are five advanced caching types:

Site caching Same as the basic web content cache except that cache parameters in connect tags and URL requests can be used to override the server's default advanced web content caching settings.
Session caching 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 caching 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 caching 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 caching Used to cache web pages of users who have the same "personalization profile". This means that 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 the server's default advanced web content caching settings allowing us to set custom cache settings for individual web pages or components.
In most cases, basic, site and session caching would only be used as the 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 the default web content cache, custom caching cannot be used.
See Web content cache configuration and Using custom caching for further information.

Cache comparisons

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

Parent Topic
Caching options

Site caching	Same as the basic web content cache except that cache parameters in connect tags and URL requests can be used to override the server's default advanced web content caching settings.
Session caching	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 caching	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 caching	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 caching	Used to cache web pages of users who have the same "personalization profile". This means that users who have selected the same personalization categories and keywords, and who belong to the same group, share a single cache.

	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