This repository has been archived by the owner on Jun 1, 2023. It is now read-only.
Changing persistent storage paradigm #31
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Going from letting modules in the package store information in persistent storage to make the front end responsible instead.
The package will now only supply dump, flush and load methods on central classes.
Front end software can use these to get the state of the package, store it in a database of its own choosing and later use the store information to get the package back into a certain state.
Dump produces information as a dictionary that can be transfered into a string by using JSON.
Load expects to be fed a dictionary of the form that dump produces.