Skip to content

Add subscription delivery latency preference#293

Merged
connor4312 merged 2 commits into
mainfrom
subscribe-delivery-max-latency
Jul 1, 2026
Merged

Add subscription delivery latency preference#293
connor4312 merged 2 commits into
mainfrom
subscribe-delivery-max-latency

Conversation

@connor4312

Copy link
Copy Markdown
Member

Adds an opt-in per-subscription delivery preference so clients can request a maximum intentional buffering/coalescing latency via SubscribeParams.delivery.maxLatencyMs.

Closes #274

Summary

  • add SubscribeParams.delivery.maxLatencyMs to the protocol surface and docs
  • regenerate JSON schemas and all generated client wire types
  • add convenience subscribe APIs for TypeScript, Rust, Swift, and Go clients
  • document Rust struct-literal migration with generated SubscribeParams::new / with_delivery helpers

Validation

  • npm run generate
  • npm run test
  • clients/typescript: npm run typecheck && npm test
  • clients/rust: cargo check --workspace
  • clients/go: go test ./...
  • swift test

connor4312 and others added 2 commits July 1, 2026 11:40
Add delivery.maxLatencyMs to subscribe params, regenerate schema and client wire types, and expose convenience APIs for clients that want to request coalesced delivery latency.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@connor4312 connor4312 merged commit 0715a0b into main Jul 1, 2026
9 checks passed
@connor4312 connor4312 deleted the subscribe-delivery-max-latency branch July 1, 2026 20:53
@connor4312 connor4312 added this to the 1.128.0 milestone Jul 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Proposal: client-controlled streaming granularity — opt into coalesced response updates

2 participants