atomic-data-docs
atomic-data-docs copied to clipboard
Initializing resources with a Commit
Currently, Commits have some serious ambiguity. They do not specify if they are editing a resource, or if they are creating a new one. This can lead to accidental overwrites of existing data. How to solve this?
Require previous commit ID / signature in each edit commit
- Makes commits more easily browseable
- It makes commits a blockchain, basically. That's a cool word!
- Means that the client has to find this commit. That means adding logic to the client, which now has to query some endpoint of a server to find the latest commit for a resource. Which takes precious cycles.
Require 'init' boolean in initialization commits
- Very lightweight to implement