summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2017-03-30 12:51:14 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2017-03-30 12:51:14 -0400
commit4a52a954e3014ba7a7313445b7d02fafd6f4cfa9 (patch)
tree6a523255b2c68cb0dc0dfaaaae470db0456f3f90 /doc
parent48f3b59749fd0c203afed1e050cd0c33abff2f3b (diff)
parentb058f1a97338b5aad54c92affc4a3a6fc75943a3 (diff)
Merge branch 'master' of ssh://git-annex.branchable.com
Diffstat (limited to 'doc')
-rw-r--r--doc/todo/multicast___34__broadcasting__34___of_content_on_local_net.mdwn7
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/todo/multicast___34__broadcasting__34___of_content_on_local_net.mdwn b/doc/todo/multicast___34__broadcasting__34___of_content_on_local_net.mdwn
new file mode 100644
index 000000000..fa240bdf5
--- /dev/null
+++ b/doc/todo/multicast___34__broadcasting__34___of_content_on_local_net.mdwn
@@ -0,0 +1,7 @@
+Hi Joey,
+
+Although I haven't remembered that "hash thing" to perform the job, we looked around for other ways to accomplish the mission: quickly/simultaneously distribute annexed files to multiple hosts on the same network. So, there are such tools as uftp to efficiently multicast files to multiple recipients. Initial setup takes a bit but I wondered how feasible it could be to e.g. establish some "custom annex remote" (if to avoid coming up with a new command eg. "annex serve") so e.g. I could e.g. `git annex copy --to=udp-multicast ` on the host A which has all the keys, and then run `git annex get --from=udp-multicast` on the clients (B) which want to get it all. To make it even more efficient, A could may be provide/announce on the local net a service to receive requests for desired keys to be transmitted. But even if it just multicasts all the content of the current tree, while those clients suck them all in, it could be super useful.
+
+What do you think?
+
+[[!meta name=yoh]]