summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar http://phil.0x539.de/ <Philipp_Kern@web>2012-12-28 23:23:29 +0000
committerGravatar admin <admin@branchable.com>2012-12-28 23:23:29 +0000
commitf657b4022c8e1088a31e63f4848cab74ce6f1033 (patch)
tree5da1f1d5e6838985574fbe781ba02e52ac233504
parent7b7be8e2fb876aa089869d5422c98c8ffbed1a87 (diff)
Added a comment
-rw-r--r--doc/todo/resuming_encrypted_uploads/comment_1_1832a6fb78e8ad7c838582f46731ac3b._comment8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/todo/resuming_encrypted_uploads/comment_1_1832a6fb78e8ad7c838582f46731ac3b._comment b/doc/todo/resuming_encrypted_uploads/comment_1_1832a6fb78e8ad7c838582f46731ac3b._comment
new file mode 100644
index 000000000..cf35de049
--- /dev/null
+++ b/doc/todo/resuming_encrypted_uploads/comment_1_1832a6fb78e8ad7c838582f46731ac3b._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="http://phil.0x539.de/"
+ nickname="Philipp Kern"
+ subject="comment 1"
+ date="2012-12-28T23:23:29Z"
+ content="""
+Doesn't the encryption part already write an encrypted version completely to disk before starting to upload? (At least with the rsync remote?) So the disk space and I/O usage is already there. (Except that it's probably a temporary file that's deleted after it was created, so that it's not kept around by the filesystem when certain destructive events strike.)
+"""]]