2012-05-27 01:11:19 +00:00
|
|
|
Currently, git-annex takes a very lazy approch to displaying
|
|
|
|
|
progress into. It just lets rsync or whatever display the progress
|
|
|
|
|
for it, in the terminal.
|
|
|
|
|
|
|
|
|
|
Something better is needed for the [[webapp]]. There needs to be a
|
|
|
|
|
way for the web app to know what the current progress is of all transfers.
|
|
|
|
|
|
2012-08-28 18:04:28 +00:00
|
|
|
This is one of those potentially hidden but time consuming problems.
|
2012-05-27 01:11:19 +00:00
|
|
|
|
2012-08-28 18:04:28 +00:00
|
|
|
## downloads
|
2012-05-27 01:11:19 +00:00
|
|
|
|
2012-08-28 18:04:28 +00:00
|
|
|
* Watch temp file as it's coming in and use its size.
|
|
|
|
|
This is the only option for some special remotes (ie, non-rsync).
|
|
|
|
|
Can either poll every .5 seconds or so to check file size, or
|
2012-09-19 18:28:57 +00:00
|
|
|
could use inotify. **done**
|
|
|
|
|
|
|
|
|
|
## uploads
|
|
|
|
|
|
|
|
|
|
Options:
|
|
|
|
|
|
2012-08-28 18:04:28 +00:00
|
|
|
* Feed rsync output into a parser and parse out a progress value. Ugly,
|
|
|
|
|
failure prone, but potentially the least CPU-expensive option.
|
|
|
|
|
* Use librsync. Note: It's not wire-compatiable with the actual rsync
|
|
|
|
|
command.
|
|
|
|
|
* Set up a FIFO, have rsync read from or write to that, and the FIFO
|
|
|
|
|
feeder/reader then can update the transfer info. Generic enough to
|
|
|
|
|
work for most (all?) special remotes, but also the most expensive option,
|
|
|
|
|
involving another copy through memory of the whole file contents.
|
