{{ReleaseStatus/Beta}}
The View Cache feature increases the performance of the [[web Service]] by caching the data to be published and sent to the clients. All content data as well as the hierarchies, as defined by the [[View]] and in the [[ACM]], is evaluated and cached internally. A client's request for hierarchical data, covering '''two or more hierarchy''' levels, will be handled using the cached data. Any request covering only one hierarchy level will by-pass the view cache and be treated directly. For example, browsing through the objects using the [[Content Browser]] does not use the View Cache, whereas preparing the [[HowTo:Switch_to_Offline_Mode|Offline Mode]] utilizes the cache to improve performance. Once the cache has been initialized, its status and additional information can be retrieved by web service methods.{{Attention|Up to now the View Cache needs to be initialized and updated manually after every restart (re)start of the web service, due to a missing automatism!}}
== Using the View Cache ==
Once initialized, a client's request for hierarchical data will be handled using the cached data. This data encompasses all content data and its hierarchies, but not the physical documents linked to the objects. Hence, if the client is actually fetching data from the web service the documents have to be loaded.
=== Initialization / Update of View Cache ===
The cache needs to be initialized after a web service has been (re)started. This can be achieved by calling [[#TriggerViewStateUpdate]]
=== ===
=== Enabling ==