DS4: the warm call is served from the cache rather than silently refetched.
Told apart from outside the provider by making the cached copy distinguishable from what the
server would return: a sentinel is written into the cached blob's Status, and the warm call must
return it. The server's own status coming back means the cache missed.
The sentinel leaves every per-entity row count untouched. Freshness compares those counts against
the server to catch pure deletes, so changing one would invalidate the cache and the check would
say nothing about serving.
Clears the cache in a finally, so no sentinel-bearing copy is left for the metadata bootstrap or
a later bundle to read.
DS4: the warm call is served from the cache rather than silently refetched.
Told apart from outside the provider by making the cached copy distinguishable from what the server would return: a sentinel is written into the cached blob's
Status, and the warm call must return it. The server's own status coming back means the cache missed.The sentinel leaves every per-entity row count untouched. Freshness compares those counts against the server to catch pure deletes, so changing one would invalidate the cache and the check would say nothing about serving.
Clears the cache in a
finally, so no sentinel-bearing copy is left for the metadata bootstrap or a later bundle to read.