{{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. Be aware, that this data does not encompass the physical documents linked to the objects, hence the documents have to be loaded if the requested from the client.
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.
== 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 the method [[#TriggerViewStateUpdate]].
=== Enabling ===
The View Cache features needs to be enabled in the [[Configuration_File_Example#tab=web_config|web.config]] file of the corresponding web service.
</syntaxhighlight>
=== Testing ===Test the View Cache's result for a single object, given by its {{Guid}}, via the method [[#TestViewState]].The result will not retrieve the physical documents.
== Web Service Interface ==
=== TestViewState===
Test the View Cache's result for a single object (given by its {{Guid}}), without retrieving the physical documents.
<syntaxhighlight lang="csharp">
/// <summary>