Load and persist peer vector clocks #86
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
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.
Following the same approach taken by
ssb-ebt(used in Manyverse), we persist peer vector clocks to theebtdirectory in the application's root configuration directory (~/.local/share/solarin the case of solar).Each file is created using the @-prefixed SSB ID of the author as the filename; all instances of
/are replaced with-and the=before.ed25519is removed. For example:@HIYqoOhH6U-muCXsnvXzRQmoPpPXrELnJlqSjId2Fg8.ed25519The file then contains a JSON string of the vector clock for that peer. For example:
{"@HIYqoOhH6U+muCXsnvXzRQmoPpPXrELnJlqSjId2Fg8=.ed25519":32,"@HZnU6wM+F17J0RSLXP05x3Lag2jGv3F3LzHMjh72coE=.ed25519":7712}Clocks are loaded from file when the EBT manager starts and persisted to file just before it shuts down.