In the CHA, there are data that are always read only and are never modified. In a read-only remote CHA context, the client side can cache this type of data to reduce the amount of communication between the client side and server side of the context.
When a request for data arrives at a read-only client side CHA context, it looks in its read cache. If the data exists in the cache, the client returns the cached data. If the data is not in the cache, the client obtains the data from the server side context. The client side caches the data and sends it to the requester. The cache has the same lifetime as its corresponding CHA context instance. That is, the system creates the cache when it creates the context and removes the cache when it cleans up the context.