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 #1

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Fix typo #1

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 README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,6 @@ tests - Some automated tests, using the pytest framework.

* **tb** - The prefix we used to namespace Rising Thunder code during development. Everywhere you see "tb" you can think "rt" and be pretty safe (e.g. tbrpc describes the RT RPC layer). What tb stands for remains a mystery.
* **rpc** - Most of the non-game functionality of the server is implemented with an RPC layer over HTTP built using Google Protocol Buffers. Whenever the code refers to RPCs, it's talking about that.
* **portal** - Most of the game-dependant functionality of the server. The portal is a UDP server which facilates game creation, spectating, detecting disconnected players, and implements the state machine required to implement RT's 2/3 games per-match flow. Its implementation is greatly complicated by the fact that UDP is a lossy protocol. Much of the state machine should probably have been implemented with RPCs, but c'est la' vie.
* **portal** - Most of the game-dependant functionality of the server. The portal is a UDP server which facilitates game creation, spectating, detecting disconnected players, and implements the state machine required to implement RT's 2/3 games per-match flow. Its implementation is greatly complicated by the fact that UDP is a lossy protocol. Much of the state machine should probably have been implemented with RPCs, but c'est la' vie.