The AppServer cache operates as an on-demand cache by default. Content is loaded and stored only when requested by a client. This approach reduces resource consumption and ensures that only content that is actually needed is cached.

In practice, this means: If a client requests content that is not yet available on the cache server, the cache server queries the backend server. The result is stored in the cache. If another client requests the same content, it is delivered directly from the local cache—eliminating the need for a network round trip.

A key feature is the consideration of user rights and permission groups. Cache content can be managed separately, ensuring that protected information is not delivered to unauthorized users.