Repository navigation
Fix cancellable read sharing and static cache recovery - #251
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Concurrent cancellable reads currently bypass transport sharing, live change refreshes can join reads that started before the change, and missing static assets are served with a year-long immutable cache policy. This shares ordinary GET transports while preserving each caller’s cancellation and independent result, fences both clients’ live refreshes by mutation generation, and keeps fresh/header-specific evidence out of ordinary ETag reuse.
no-storeandVary: *replies are no longer retained.Successful hashed assets keep immutable caching; missing/error assets and icons now use
no-store. Also fixes the Library toggle overlapping its heading at 320px width.Validation: 26 focused transport/profile/live-dispatch checks; shared package build; backend, desktop and mobile type checks; desktop production build; formatting and source ownership checks. Exact production nginx image passed 24 before and 24 after HTTP cases, including successful, conditional, partial and error responses, nested asset URLs, unchanged HTML/API policies and security headers. An equivalent three-cancellable-reader fixture used 3 fetches before and 1 after. Production UI and asset-header checks will follow the authorized
update.batrollout. Hosted CI is not awaited at the owner’s request; no retained authority TTL or profile-latency improvement is claimed.