With one Docbase and multiple Content Servers running in Distributed configuration the same dm_cache_config objects would apply to all the client sessions regardless of which eCS they are connected to. So the cache update on the client would be consistent for all the users. The persistent cache is on the client machine, but the client dmcl does check the r_last_changed_date of the server’s cache config object as part of the logic to determine if the local cache is out-of-date. Basically, the client dmcl does two checks. First it checks how old the local cache is by comparing the time stamp of the local cache to the server_check_interval attribute copied from the server’s cache config object. This is all done locally on the client machine because the client dmcl has a copy of this value. The server_check_interval is just maximum length of time the local cache is good for. If the local cache isn’t expired based upon this first check, then it looks at the r_last_changed_date of the server’s config object to determine if it has changed. It might have changed because of a job, or an administrator may have forced the update.