Fix Streamable HTTP WebClient GET SSE handling #318
Merged
+75
−14
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.
The WebClient Streamable HTTP implementation was missing the incoming message handling on the SSE channel opened with
GET
HTTP method. This caused sampling to not work when used against the typescript-sdk basedeverything
serverThe specification uses the word
SHOULD
when talking about requests from the server to the client that they should use the same stream which is used for the related client request (tool call in this case) but apparently the typescript-sdk uses a different SSE connection to send the createMessage request. We should handle that properly.Also, this PR fixes a problematic
DELETE
method handling in which the current session was replaced with an uninitialized one first before closing the existing session. That call would then extract the session id to sendDELETE
for, but it used the uninitialized one instaed of the one being closed. This PR fixes it too.