aboutsummaryrefslogtreecommitdiffstats
path: root/proposals/0000-multiwriter.md
diff options
context:
space:
mode:
Diffstat (limited to 'proposals/0000-multiwriter.md')
-rw-r--r--proposals/0000-multiwriter.md6
1 files changed, 2 insertions, 4 deletions
diff --git a/proposals/0000-multiwriter.md b/proposals/0000-multiwriter.md
index d2e6318..e8f931a 100644
--- a/proposals/0000-multiwriter.md
+++ b/proposals/0000-multiwriter.md
@@ -98,7 +98,8 @@ perspective of that writer at the time they created the entry, in the form of
"clock" version pointers. This metadata (a "[vector clock][vc]") can be used by
other writers to resolve (or at least identify) conflicting content in the
database. The technical term for this type of system is a "Conflict-free
-replicated data type" ([CRDT][crdt]).
+replicated data type" ([CRDT][crdt]), and specifically an "Operation-based" (as
+opposed to "State-based") CRDT.
[vc]: https://en.wikipedia.org/wiki/Vector_clock
[crdt]: https://en.wikipedia.org/wiki/Conflict-free_replicated_data_type
@@ -466,9 +467,6 @@ for being more difficult to understand and implement.
# Unresolved questions
[unresolved]: #unresolved-questions
-What is the technical term for the specific CRDT we are using?
-"Operation-based" or "State-based"?
-
What is the actual on-disk layout (folder structure), if not what is documented
here?