mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

update

Browse source
This commit is contained in:
Joey Hess 2012-07-07 10:56:09 -06:00
parent 583cfb5667
commit eb9063c0d1
1 changed files with 9 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

17
doc/design/assistant/syncing.mdwn
View file

@ -1,23 +1,24 @@
Once files are added (or removed or moved), need to send those changes to Once files are added (or removed or moved), need to send those changes to
all the other git clones, at both the git level and the key/value level. all the other git clones, at both the git level and the key/value level.
## action items ## immediate action items
* Check that download transfer triggering code works (when a symlink appears * Check that download transfer triggering code works (when a symlink appears
and the remote does *not* upload to us. and the remote does *not* upload to us.
* Investigate why transfers seem to block other git-annex assistant work.
* At startup, and possibly periodically, look for files we have that * At startup, and possibly periodically, look for files we have that
location tracking indicates remotes do not, and enqueue Uploads for location tracking indicates remotes do not, and enqueue Uploads for
them. Also, enqueue Downloads for any files we're missing. them. Also, enqueue Downloads for any files we're missing.
* Find a way to probe available outgoing bandwidth, to throttle so * The TransferWatcher does not notice ongoing transfers, because inotify is
we don't bufferbloat the network to death. waiting for the info file to be closed, but that never happens, it's left
* git-annex needs a simple speed control knob, which can be plumbed open to keep it locked.
through to, at least, rsync. A good job for an hour in an
airport somewhere.
* file transfer processes are not waited for, contain the zombies.
## longer-term TODO ## longer-term TODO
* git-annex needs a simple speed control knob, which can be plumbed
through to, at least, rsync. A good job for an hour in an
airport somewhere.
* Find a way to probe available outgoing bandwidth, to throttle so
we don't bufferbloat the network to death.
* Investigate the XMPP approach like dvcs-autosync does, or other ways of * Investigate the XMPP approach like dvcs-autosync does, or other ways of
signaling a change out of band. signaling a change out of band.
* Add a hook, so when there's a change to sync, a program can be run * Add a hook, so when there's a change to sync, a program can be run