feat: enhance BatchedPollingEventSubscriber initialization in PollingJsonRpcProvider #123
+71
−26
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 refactors and improves the event polling logic in the provider implementation. The main focus is on making event polling more efficient, robust, and easier to manage by introducing batching, error handling, and improved timer management.
Event Polling Efficiency and Batching
BatchedPollingEventSubscribernow batcheseth_getLogscalls, processing events in chunks of up to 500 blocks (DEFAULT_MAX_BATCH_BLOCKS). This reduces the number of RPC calls and improves performance for large block ranges. [1] [2]Robustness and Error Handling
Integration and Pause Support
BatchedPollingEventSubscriberinPollingJsonRpcProvider, the subscriber respects the provider's paused state and can be paused immediately if required.