[Cached Navs] Don't extract static stage (#99617)
The original `cachedNavigations` experiment had a behavior where if the feature was not enabled for a particular route, the client would cache just the static part of the response, since it could be expressed as a single byte offset without any additional overhead. We've since decided Cached Navigations is too important of a feature to be opt-in per route. So now it's always enabled (whenever Partial Prefetching is enabled). Therefore it no longer makes sense to extract the static part of the response. Instead, we'll do the same thing prefetch responses do, and extract out the shell, since the shell can be reused across different params values for the same route. This commit starts by removing the static stage extraction from the client. Subsequent steps will unify Cache Navigations extraction with the corresponding part of the prefetching implementation. When Partial Prefetching is enabled, every navigation response can be written into the cache: either the entire response is cachable, or it contains an embedded inner response that is cacheable. Conceptually it's as if each navigation is accompanied by a corresponding prefetch, and both requests are returned in the same response. This unifies the implementation used to write the response (whether it comes from a navigation or a prefetch) into the client cache.
Showing
This diff is collapsed.
This diff is collapsed.
Please
register
or
sign in
to comment