aboutsummaryrefslogtreecommitdiff
path: root/doc/metadata
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2015-05-01 15:41:49 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2015-05-01 15:41:49 -0400
commitc74164c6a59b8aa7b1d64e6703b9823ad6d580c1 (patch)
tree1f5528f09734a60b8049d40dda46d338deb49128 /doc/metadata
parent742bdf6353ac8e08fb603fe60b53c1495d4fa801 (diff)
followup
Diffstat (limited to 'doc/metadata')
-rw-r--r--doc/metadata/comment_4_237721c5e8f66f303a1828810573a23d._comment15
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/metadata/comment_4_237721c5e8f66f303a1828810573a23d._comment b/doc/metadata/comment_4_237721c5e8f66f303a1828810573a23d._comment
new file mode 100644
index 000000000..d2c13888e
--- /dev/null
+++ b/doc/metadata/comment_4_237721c5e8f66f303a1828810573a23d._comment
@@ -0,0 +1,15 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 4"""
+ date="2015-05-01T19:38:36Z"
+ content="""
+@madduck, you could file a todo if you want about that.
+
+However, I have my doubts; if the json supposed to include the full set of
+metadata for the file? If so, that seems a potentially expensive interface.
+If not, it would be hard to tell when metadata should be deleted, or when
+multiple values are being set, vs a value being changed.
+
+The current interface to set metadata deals with these possibilities in a
+compact and sensible way.
+"""]]