docs: clarify JsonRpcProvider vs WebSocketProvider behavior#5067
Open
stalim17 wants to merge 1 commit intoethers-io:mainfrom
Open
docs: clarify JsonRpcProvider vs WebSocketProvider behavior#5067stalim17 wants to merge 1 commit intoethers-io:mainfrom
stalim17 wants to merge 1 commit intoethers-io:mainfrom
Conversation
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.
This PR adds a short note to the documentation clarifying the behavioral
difference between JsonRpcProvider and WebSocketProvider.
JsonRpcProvider relies on polling under the hood, while WebSocketProvider
enables push-based subscriptions suitable for low-latency event streams
such as pending transactions or log subscriptions.
This helps integrators choose the appropriate provider type when building
real-time UX. Documentation-only change, no code modifications.