feat: Add timeout options to TypedMessenger #767
Merged
Conversation
This file contains 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
jespertheend
changed the title
jespertheend
deleted the
365-A-way-to-use-TypedMessenger-without-responses
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When the other end of the connection is untrusted, we can't assume that they will always respond to every request.
And even if the other end is trusted, the connection might still drop before the typedmessenger is destroyed.
This change adds two options:
globalTimeoutoption in the constructor of theTypedMessenger, or theTypedMessenger.globalTimeoutvalue which can be modified directly.TypedMessenger.sendWithTransferis now renamed toTypedMessenger.sendWithOptionsand a timeout can be provided for specific requests.