Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix typo in RPC #77

Merged
merged 1 commit into from
Jun 16, 2024
Merged

Fix typo in RPC #77

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion e2e/rpc.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -170,7 +170,7 @@ that networks are not perfect channels. Two such functions are:
- Support large message sizes through fragmentation and reassembly

An RPC protocol might “define this problem away” by choosing to run on
top of a reliable protocol like TCP, but in many cases, the RCP protocol
top of a reliable protocol like TCP, but in many cases, the RPC protocol
implements its own reliable message delivery layer on top of an
unreliable substrate (e.g., UDP/IP). Such an RPC protocol would likely
implement reliability using acknowledgments and timeouts, similarly to
Expand Down