Improve SSE response handling and URI construction in SseClientSessio… #251
+5
−7
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.
This pull request includes several changes to the
SseClientSessionTransport
class to improve the handling of SSE messages and URI composition. The most important changes include enhancing the conditions for checking response content and refactoring the URI composition logic.Enhancements to response content checks:
responseContent
is either empty or equals "accepted" in two locations within theSendMessageAsync
method. [1] [2]Refactoring URI composition:
HandleEndpointEvent
method to useUriBuilder
for more robust URI composition, including removing the manual string concatenation and handling the "/sse" suffix more effectively.