summaryrefslogtreecommitdiff
path: root/doc/design/assistant/transfer_control.mdwn
Commit message (Collapse)AuthorAge
* read through all design docs and updated done itemsGravatar Joey Hess2012-11-30
|
* webapp and assistant glacier supportGravatar Joey Hess2012-11-24
|
* add ConfigMonitor threadGravatar Joey Hess2012-10-20
| | | | | | | | | | | | | | | | | | | | Monitors git-annex branch for changes, which are noticed by the Merger thread whenever the branch ref is changed (either due to an incoming push, or a local change), and refreshes cached config values for modified config files. Rate limited to run no more often than once per minute. This is important because frequent git-annex branch changes happen when files are being added, or transferred, etc. A primary use case is that, when preferred content changes are made, and get pushed to remotes, the remotes start honoring those settings. Other use cases include propigating repository description and trust changes to remotes, and learning when a remote has added a new special remote, so the webapp can present the GUI to enable that special remote locally. Also added a uuid.log cache. All other config files already had caches.
* blog for the dayGravatar Joey Hess2012-10-19
|
* check preferred content when a file is moved or createdGravatar Joey Hess2012-10-19
| | | | | | | | | This can result in the file being dropped, or being downloaded, or even being dropped from some other repo. It's even possible to create a file in a directory where content is not wanted, which will make the assistant immediately send it elsewhere, and then drop it.
* raceGravatar Joey Hess2012-10-19
|
* check and drop after uploadsGravatar Joey Hess2012-10-18
|
* updateGravatar Joey Hess2012-10-18
|
* check and drop unwanted content from remotes after receiving a transferGravatar Joey Hess2012-10-18
|
* splitGravatar Joey Hess2012-10-18
|
* drop unwanted content in the transfer scanGravatar Joey Hess2012-10-18
| | | | | | | | This was complicated quite a bit by needing to check numcopies. I optimised that, so it only looks up numcopies once per file, no matter how many remotes it checks to drop from. Although it did just occur to me that it might be better to first check if it wants to drop content, and only then check numcopies..
* minor transfer scanner code reworkingGravatar Joey Hess2012-10-18
| | | | Also a small optimisation using a Set
* releasing version 3.201210163.20121016Gravatar Joey Hess2012-10-16
|
* full analysis of ways content could stop being preferred and need to be droppedGravatar Joey Hess2012-10-13
|
* webapp automatic groupingGravatar Joey Hess2012-10-09
| | | | | | | | webapp: Adds newly created repositories to one of these groups: clients, drives, servers This is heuristic, but it's a pretty good heuristic, and can always be configured.
* assistant: Now honors preferred content settings when deciding what to transfer.Gravatar Joey Hess2012-10-09
| | | | | | | | | Both when queueing downloads, and uploads, consults the preferred content settings. I didn't make it check yet when requeing failed transfers or queuing deferred downloads; dealing with the preferred content settings (or indeed, other settings) changing while the assistant is running still needs work.
* add --ingroup limitGravatar Joey Hess2012-10-08
|
* Added --smallerthan and --largerthan limitsGravatar Joey Hess2012-10-08
|
* blog for the dayGravatar Joey Hess2012-10-04
|
* terminologyGravatar Joey Hess2012-10-01
|
* added new transfer control page to webappGravatar Joey Hess2012-09-23
I have a preliminary design that looks pretty good