DescriptionRevalidate using the same Resource, attempt #3
Currently, when we perform a revalidation, we create a new resource and put it in the MemoryCache in place of the resource being revalidated. If the revalidation results in a 304, we silently swap all of the clients of the revalidation to the now-revalidated resource and swap which Resource is in the MemoryCache.
This changes the behavior to use the existing resource to revalidate itself, which simplifies the logic quite a bit. It also gives us the option of removing ResourcePtr (which is used to implement the silent client swap in the 304 case) and make Resources simply RefCounted in a future change.
BUG=
Committed: https://crrev.com/71adea27213b2268bda765abccd5a3bf9517b860
Cr-Commit-Position: refs/heads/master@{#354615}
Patch Set 1 #Patch Set 2 : #Messages
Total messages: 12 (2 generated)
|