diff options
| author |  Joey Hess <joey@kitenet.net> | 2012-09-20 23:42:34 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2012-09-20 23:42:34 -0400 |
| commit | f49c0f22bf666950e015710d126e50ecf1ab21c9 (patch) | |
| tree | 3b7f983e2b75703485bf092425581cb0a60c3c94 /doc | |
| parent | a6202ffe1b5315f199b9bc9124c58f2b0772c523 (diff) | |
a much crazier, but also more feasable idea
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/design/assistant/progressbars.mdwn | 11 |
1 files changed, 10 insertions, 1 deletions
diff --git a/doc/design/assistant/progressbars.mdwn b/doc/design/assistant/progressbars.mdwn index 592a8ce24..7ac41d4f0 100644 --- a/doc/design/assistant/progressbars.mdwn +++ b/doc/design/assistant/progressbars.mdwn @@ -26,7 +26,16 @@ the ProgressCallback as the upload progresses. Maybe I should write a proxy for the rsync wire protocol that can tell what chunk of the - file is being sent, and shim it in front of the rsync server? + file is being sent, and shim it in front of the rsync server? Sadly, + the protocol is insane. + + Another idea: Invert things. Make `git-annex-shell sendkey` run + `rsync -e 'cat'`, so it treats the incoming ssh connection as the server. + (cat probably won't really work; bidirectional pipe needed). + Run rsync in `--server` mode on the *client* side, piped to ssh. + Now the `git-annex` side doesn't have a progress bar (but it can poll the + file size and produce its own), `git-annex-shell` side does have a progress + bar. * rsync: **done** * directory |