Repository navigation
Support last event Id for resumability of sse - #830
Closed
bperhaps wants to merge 4 commits into
Closed
bperhaps wants to merge 4 commits into
bperhaps wants to merge 4 commits into
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
Copy link
Copy Markdown
Contributor
|
Resumability is abandoned in the upcoming 2026-07-28 spec, see spec > transport > streamable > earlier revisions. We don't want to invest in resumability support if it's bound to go away ; our session storage wouldn't allow it at scale anyway. |
Sorry, something went wrong.
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
2 participants
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.
Implemented SSE resumability/redelivery support for Streamable HTTP by introducing an event-store abstraction, adding in-memory event persistence/replay, wiring Last-Event-ID handling through server session/transport layers, and adding comprehensive unit/integration tests.
I haven't discussed this PR enough, so I haven't created enough Java doc documentation and tests. If there's a chance this PR will be merged, I'll try to improve it.
Motivation and Context
Implementation of MCP documentation.
How Has This Been Tested?
I worte some tests, and also i play it on my device.
Breaking Changes
nop
Types of changes
Checklist
Additional context