Make websocket optional for realtime fetcher #1778
Merged
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.
Realtime fetcher already uses both websocket and JSONRPC polling for more reliable new block fetching.
Though, if no websocket was available, the realtime fetcher wouldn't start, and no new blocks arrived at all.
As we already have a polling fallback, we now make websocket optional.
This will also help with supporting nodes without websocket API.
To disable websocket API, pass
nil
insubscribe_named_arguments.transport
.Checklist for your PR
CHANGELOG.md
with this PR