Refactor rpc_request method to allow use in threadsafe queue #409
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
…readsafe queue Allow all calls to rpc_request() to be queued and be threadsafe. Redirect the recursive call from the result_handler to the websocket sub-function. Add thread_safe_substrate_interface.py as an example.
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.
Refactor
rpc_requestmethod to allow the use of the library with a thread-safe queue.Allow all calls to
rpc_request()to be queued and be thread-safe.Redirect the recursive call from the
result_handlerto therpc_request_websocketsub-function.Add
thread_safe_substrate_interface.pyas an example.