Repository navigation
Stream-driven live updates, shared freshness reads and ETag/304 for console reads - #72
Merged
Merged
Conversation
…er freshness reads Client: remove the fixed 5s poll loops; task-freshness polls (with jitter) only while the SSE stream is unavailable or stalled. Server: coalesce freshness token reads per organization per process so open streams share database reads, and jitter stream lifetime to avoid synchronized reconnects. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Uu9rHW673neRB1LQgE3N1k
task-views, decisions and notifications return a weak body ETag and answer 304 to If-None-Match while staying no-store. The client revalidates from tab memory (nothing is written to browser storage) and skips re-rendering on 304. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Uu9rHW673neRB1LQgE3N1k
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Uu9rHW673neRB1LQgE3N1k
Member
Author
|
CI on the latest head: Generated by Claude Code |
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.
What changed and why
The console polled
task-views,decisionsandnotificationsevery 5 seconds per tab on top of the SSE signal, and each open stream read the freshness token from the database every 500 ms. Both costs grew with the number of open tabs.task-freshnesspolls (5–7.5 s, jittered) only while the stream is unavailable, stalled (no frame for 20 s) or failing to reconnect (5 s). Focus and signal refetches stay.CoalescedFreshnessReadershares token reads between streams, so the database sees at most one read per organization per 400 ms per web process. Stream lifetime is now randomized (40–55 s) so streams opened together (for example after a rollout) do not reconnect together.task-views,decisionsandnotificationssend a weak bodyETagand answer304toIf-None-Match. Responses stayno-store; the client revalidates from tab memory, so the browser stores nothing, and skips re-rendering on304.CHANGELOG.mdupdated.Remaining work is tracked in #71 (skipping the query on unchanged reads, per-resource invalidation, LISTEN/NOTIFY, load numbers).
How it was verified
npm run lint,npx tsc --noEmit,npm test(624 tests),npm run build: pass.npm run test:http: all scripts pass, including a new304check on/api/task-views.freshness.db.test.tson PGlite: pass.npm run test:db,db:migrateanddb:schema:check(no code in this change touches them), and nothing against a real PostgreSQL or multiple replicas.Checklist
npm run checkpasses (the part I could run is listed above)docs/security/threat-model.md(not applicable: responses stayno-store, nothing is written to browser storage)CHANGELOG.mdGenerated by Claude Code