The cache-provider-class Element"
From Documentation
m |
|||
Line 6: | Line 6: | ||
[Default: <javadoc>org.zkoss.zk.ui.impl.SessionDesktopCacheProvider</javadoc>] | [Default: <javadoc>org.zkoss.zk.ui.impl.SessionDesktopCacheProvider</javadoc>] | ||
− | It specifies which class used to implement the desktop cache. The class must have a default constructor (without any argument), and implement the <javadoc type="interface">org.zkoss.zk.ui.sys.DesktopCacheProvider</javadoc> interface. | + | It specifies which class is used to implement the desktop cache. The class must have a default constructor (without any argument), and implement the <javadoc type="interface">org.zkoss.zk.ui.sys.DesktopCacheProvider</javadoc> interface. |
One instance of the cache provider is created and shared for each Web application, so you have to synchronize the access properly. | One instance of the cache provider is created and shared for each Web application, so you have to synchronize the access properly. |
Revision as of 03:28, 8 August 2011
Syntax:
<cache-provider-class>a_class_name</cache-provider-class>
[Default: SessionDesktopCacheProvider]
It specifies which class is used to implement the desktop cache. The class must have a default constructor (without any argument), and implement the DesktopCacheProvider interface.
One instance of the cache provider is created and shared for each Web application, so you have to synchronize the access properly.
Available implementations are as follows.
SessionDesktopCacheProvider | It stores all desktops from the same session in one single cache. It is simple and fast, but not supporting clustering. |
GlobalDesktopCacheProvider | It stores all desktops from the same Web application in one single cache. In other words, it doesn't count on session at all.
It is useful because some Web server, e.g, BEA WebLogic, might be configured to use independent sessions for each request. |
Version History
Version | Date | Content |
---|---|---|