modelcontextprotocol/ruby-sdk
Watch
1
0
Fork
You've already forked ruby-sdk
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

[Doc] State the Listen Stream Delivery Semantics

Browse source 
The Subscriptions page documented the acknowledgement-first contract but not what delivery means:
the stream carries only changes that happen after the acknowledgement, nothing is queued while
no stream is connected, and a dropped stream is gone together with anything it missed.
The Python SDK's subscriptions page states the same contract ("It is not a replay log").
Spelling it out gives client implementers the fetch-after-subscribing guidance and
makes the acknowledgement-window behavior explicit.
This commit is contained in:
Koichi ITO 2026-09-13 17:10:12 +09:00
commit ef3eb7b0b2
1 changed files with 7 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

7
docs/_server/subscriptions.md
View file

@ -49,6 +49,13 @@ The first SSE event on the stream is the acknowledgement:
}
```
## Delivery Semantics
A stream delivers only the changes that happen after its acknowledgement; it is not a replay log.
Nothing is queued while no stream is connected, and a dropped stream is gone together with anything it missed.
Clients fetch the current state after subscribing and treat each notification as a cue to refetch,
rather than as a payload.
## Transport Support
The stream is served on the Streamable HTTP modern path; stdio answers `-32601`.