feat(jsonrpc): add tracked response receipts - #338
Open
danielkov wants to merge 1 commit into
Open
Conversation
This was referenced Aug 26, 2026
danielkov
marked this pull request as ready for review
August 26, 2026 12:47
11 tasks
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
1 participant
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.
Summary
Adds optional responder APIs that return a receipt for the outgoing JSON-RPC response:
Responder::respond_trackedResponder::respond_with_result_trackedResponseReceiptAwaiting the receipt confirms that the response frame has been queued for transport. For a batched request, the receipt waits until the complete batch response is assembled and queued, not merely until one response entry is ready.
The existing responder APIs keep their current behavior. Callers only pay for tracking when they use the new methods.
This gives handlers an ordering point for follow-up work that must happen after the response, such as emitting a notification that refers to a newly accepted resource.
Related