aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorBryan Newbold <bnewbold@robocracy.org>2018-07-06 11:35:38 -0400
committerBryan Newbold <bnewbold@robocracy.org>2018-07-06 11:35:38 -0400
commiteb1334949faed0238d5251a0794067caa643b713 (patch)
tree3cfea083c5b95521bf34928336596462405e6a22
parenta81c069501ab3c99d8129fde9e4f97958f62fe5f (diff)
downloaddat-deps-eb1334949faed0238d5251a0794067caa643b713.zip
dat-deps-eb1334949faed0238d5251a0794067caa643b713.tar.gz
multiwriter on-disk folder structure
-rw-r--r--proposals/0000-multiwriter.md13
1 files changed, 9 insertions, 4 deletions
diff --git a/proposals/0000-multiwriter.md b/proposals/0000-multiwriter.md
index 8264786..eb25c3d 100644
--- a/proposals/0000-multiwriter.md
+++ b/proposals/0000-multiwriter.md
@@ -202,10 +202,15 @@ The fields of interest for multi-writer are:
self-reference to the current (local) Feed's key, always as the first
element.
-When serialized on disk in a SLEEP directory, the original feed is written
-under `source/`. If the "local" feed is different from the original feed (aka,
-local is not the "Original Writer"), it is written to `local/`. All other feeds
-are written under directories prefixed `peers/<feed-discovery-key>/`.
+When serialized on disk in a SLEEP directory:
+
+- `source/`: the original feed, as created or cloned by this writer
+- `local/`: if "local" feed is different from "source", it goes here
+- `peers/<discover-key>/`: all other writers' feed go under this directory (the
+ discovery key is lower-case hex-encoded)
+- `content/<discovery-key>/`: if a higher-level protocol is being used that
+ uses multiple linked hypercore feeds (eg, hyperdrive), the linked "content"
+ feeds all go under this directory
## Feeds and Vector Clocks