From: Daira Hopwood <daira@jacaranda.org> Date: Sun, 25 Oct 2015 11:18:23 +0000 (+0000) Subject: remote-to-local-sync.rst: fix an inconsistency in the representation option table. X-Git-Url: https://git.rkrishnan.org/vdrive/reliability?a=commitdiff_plain;h=4ac5532fd2f961af12e26feff9384b9f4ce6b739;p=tahoe-lafs%2Ftahoe-lafs.git remote-to-local-sync.rst: fix an inconsistency in the representation option table. Signed-off-by: Daira Hopwood <daira@jacaranda.org> --- diff --git a/docs/proposed/magic-folder/remote-to-local-sync.rst b/docs/proposed/magic-folder/remote-to-local-sync.rst index d134fb9f..acc233c4 100644 --- a/docs/proposed/magic-folder/remote-to-local-sync.rst +++ b/docs/proposed/magic-folder/remote-to-local-sync.rst @@ -174,7 +174,7 @@ collapsed into the same DMD, which could get quite large. In practice a single DMD can easily handle the number of files expected to be written by a client, so this is unlikely to be a significant issue. -123â â â: In these designs, the set of files in a Magic Folder is +123â â: In these designs, the set of files in a Magic Folder is represented as the union of the files in all client DMDs. However, when a file is modified by more than one client, it will be linked from multiple client DMDs. We therefore need a mechanism, such as a @@ -231,7 +231,7 @@ leave some corner cases of the write coordination problem unsolved. +------------------------------------------------+------+------+------+------+------+------+ | Can result in large DMDs |â | | | | | | +------------------------------------------------+------+------+------+------+------+------+ -| Need version number to determine priority |â |â |â | | | | +| Need version number to determine priority |â â |â â |â â | | | | +------------------------------------------------+------+------+------+------+------+------+ | Must traverse immutable directory structure | | |â â | |â â | | +------------------------------------------------+------+------+------+------+------+------+