summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar https://www.google.com/accounts/o8/id?id=AItOawkNE-H4vEcbcGndxq5daT8qUb7yIf7r1OE <ukasz@web>2014-03-27 01:07:41 +0000
committerGravatar admin <admin@branchable.com>2014-03-27 01:07:41 +0000
commitf4fabc92500636b2b784cae555ea9b3850b71264 (patch)
treefef5b06d24501dae452cd3e8baef50dd716202bb /doc
parent04a7abaca390eac34e0a1a70b099f5c6bfd175d2 (diff)
Just some questions for clarification.
Diffstat (limited to 'doc')
-rw-r--r--doc/forum/telehash_syncing.mdwn10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/forum/telehash_syncing.mdwn b/doc/forum/telehash_syncing.mdwn
new file mode 100644
index 000000000..3a5266506
--- /dev/null
+++ b/doc/forum/telehash_syncing.mdwn
@@ -0,0 +1,10 @@
+Hi
+
+I have read some info about telehash. It looks verry promising. I was wondering though how syncing will work. For example. I have 2 computers. Normal PC and a laptop. Mostly only one is on at a time.
+
+* Sync messages will be sent over telehash protocoll ?
+* What if I push some changes (they will be synced to a shared repository) and laptop is not online. How will git-annex know what to sync from a shared repository ?
+* Do you plan to send files/commits directly to online clients ? If 2 friends are online at the same time.
+* What will happen with data on a shared repository if all clients have synced content ? Will it be deleted since it is not longer needed ?
+
+I was thinking of a model where you sync directly (if possible), and just drop shared content to repo for offline users. Whan everyone have pulled content it may be removed from shared repo.