diff options
| author | Bryan Newbold <bnewbold@robocracy.org> | 2018-03-18 21:27:19 -0700 |
|---|---|---|
| committer | Bryan Newbold <bnewbold@robocracy.org> | 2018-03-18 21:27:19 -0700 |
| commit | 5c0d406ccd09fb4ad2142591f27a80718ddef7b4 (patch) | |
| tree | 12ada29fbbcd1ad6180607e2baf1b7e04ce8002d | |
| parent | 355cb31ab7f4da540dd276f55ecb1d57999ef6a2 (diff) | |
| download | dat-deps-5c0d406ccd09fb4ad2142591f27a80718ddef7b4.tar.gz dat-deps-5c0d406ccd09fb4ad2142591f27a80718ddef7b4.zip | |
what should be resolved before Draft
| -rw-r--r-- | proposals/0000-hyperdb.md | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/proposals/0000-hyperdb.md b/proposals/0000-hyperdb.md index 277cafb..f9a180d 100644 --- a/proposals/0000-hyperdb.md +++ b/proposals/0000-hyperdb.md @@ -604,13 +604,14 @@ Further logistical details are left to the forthcoming Multi-Writer DEP. Need to think through deletion process with respect to listing a path prefix; will previously deleted nodes be occulded, or potentially show up in list -results? +results? Should be resolved before Draft. Can the deletion process (currently leaving "tombstone" entries in the `trie` forever) be improved, such that these entries don't need to be iterated over? mafintosh mentioned this might be in the works. Does this DEP need to "leave room" for those changes, or should we call out the potential for future change? -(Probably not, should only describe existing solutions) +Probably not, should only describe existing solutions. This can be resolved +after Draft. There are implied "reasonable" limits on the size (in bytes) of both keys and values, but they are not formally specified. Protobuf messages have a hard |