Make rabble functional :) #3
Merged
Conversation
This file contains 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
Rabble is now fully functional from a conceptual standpoint. It has cluster membership, lightweight processes, thread handlers that can send and receive messages, and abstractions to build client API servers, with the most fleshed out support for TCP servers. A strong effort was made to handle most errors via [error_chain](https://brson.github.io/error-chain/error_chain/index.html). Logging is done using [slog](https://brson.github.io/error-chain/error_chain/index.html) There are both single and multi-node chain replication tests and a join/leave cluster membership test. Architecture and user docs are in /doc
andrewjstone
force-pushed
the
cluster-server-rebase
branch
from
f7e99d3
to
e1474ed
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Rabble is now fully functional from a conceptual standpoint. It has
cluster membership, lightweight processes, thread handlers that can send
and receive messages, and abstractions to build client API servers, with
the most fleshed out support for TCP servers.
A strong effort was made to handle most errors via
error_chain.
Logging is done using
slog
There are both single and multi-node chain replication tests and a
join/leave cluster membership test.
What remains is full user documentation describing the system and how to
use it. That will either come in this PR or subsequent PRs.