-
Notifications
You must be signed in to change notification settings - Fork 139
[Client] Implement SSE reconnect with Last-Event-ID #327
Copy link
Copy link
Open
Labels
ClientIssues & PRs related to the Client componentIssues & PRs related to the Client componentP1Significant bug affecting many users, highly requested featureSignificant bug affecting many users, highly requested featureenhancementRequest for a new feature that's not currently supportedRequest for a new feature that's not currently supportedimproves spec complianceImproves consistency with other SDKs such as TyepScriptImproves consistency with other SDKs such as TyepScript
Metadata
Metadata
Assignees
Labels
ClientIssues & PRs related to the Client componentIssues & PRs related to the Client componentP1Significant bug affecting many users, highly requested featureSignificant bug affecting many users, highly requested featureenhancementRequest for a new feature that's not currently supportedRequest for a new feature that's not currently supportedimproves spec complianceImproves consistency with other SDKs such as TyepScriptImproves consistency with other SDKs such as TyepScript
Type
Fields
Give feedbackNo fields configured for issues without a type.
Context
Per the MCP Streamable HTTP transport spec, when an SSE stream disconnects the client SHOULD reconnect using
Last-Event-IDto resume the stream without losing notifications.src/Client/Transport/HttpTransport.php::processSSEStreamcurrently abandons the stream on EOF.Scope
id:line per active stream.GET <endpoint>+Accept: text/event-streamMcp-Session-IdheaderLast-Event-ID: <id>headerretry:SSE field when present.Conformance scenarios unblocked
sse-retry.Dependencies
Independent — can run in parallel with auth work.
Acceptance
sse-retrypasses.cc @soyuka