aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoey Hess <joey@gnu.kitenet.net>2009-12-28 13:03:39 -0500
committerJoey Hess <joey@gnu.kitenet.net>2009-12-28 13:03:39 -0500
commit87c84515e96ac991a67571b26d90a4f2ed58c757 (patch)
treea8dcacf56e0c730e30d1c93e997b9286a7efec43
parent31adf108c8760f11e677f7acdb732b28c0d365ed (diff)
downloadikiwiki-87c84515e96ac991a67571b26d90a4f2ed58c757.tar
ikiwiki-87c84515e96ac991a67571b26d90a4f2ed58c757.tar.gz
idea
-rw-r--r--doc/todo/conflict_free_comment_merges.mdwn14
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/todo/conflict_free_comment_merges.mdwn b/doc/todo/conflict_free_comment_merges.mdwn
new file mode 100644
index 000000000..e0e8acb34
--- /dev/null
+++ b/doc/todo/conflict_free_comment_merges.mdwn
@@ -0,0 +1,14 @@
+Currently, new comments are named with an incrementing ID (comment_N). So
+if a wiki has multiple disconnected servers, and comments are made to the
+same page on both, merging is guaranteed to result in conflicts.
+
+I propose avoiding such merge problems by naming a comment with a sha1sum
+of its (full) content. Keep the incrementing ID too, so there is an
+-ordering. And so duplicate comments are allowed..)
+So, "comment_N_SHA1".
+
+Note: The comment body will need to use meta title in the case where no
+title is specified, to retain the current behavior of the default title
+being "comment N".
+
+What do you think [[smcv]]? --[[Joey]]