feat: add subscription listen streams (SEP-2575)#1000
Draft
DaleSeo wants to merge 1 commit into
Draft
Conversation
DaleSeo
force-pushed
the
feat/sep-2575-subscriptions-listen
branch
from
July 17, 2026 00:48
57f0dad to
5a1ead3
Compare
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.
Motivation and Context
SEP-2575 replaces the old way of delivering notifications through
resources/subscribe,resources/unsubscribe, and standalone Streamable HTTP GET streams. It introduces a new transport-neutral request calledsubscriptions/listen. This update brings in typed models and high-level server/client APIs that ensure acknowledgment ordering, subscription ID tagging, opt-in filtering, concurrent stream isolation, cancellation, and smooth or abrupt termination for both stdio and Streamable HTTP.We still support legacy resource subscriptions, HTTP sessions, GET/DELETE, and resumable streams for older protocol versions.
How Has This Been Tested?
Add tests. The conformance suite passes
Breaking Changes
No existing stable-protocol behavior is removed. The legacy
subscribe()andunsubscribe()APIs are deprecated for the 2026 protocol revision but retain their existing wire behavior for older negotiated versions.Types of changes
Checklist