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

devblog

Browse source
This commit is contained in:
Joey Hess 2014-05-06 17:53:22 -03:00
parent 217774f72e
commit 312d82a2fd
Failed to extract signature
2 changed files with 23 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
doc/design/requests_routing.mdwn
View file

@ -28,15 +28,31 @@ Currently:
time 0|1 uuid1 time 0|1 uuid1
time 0|1 uuid2 time 0|1 uuid2
* Use negative numbers for the TTL of a request. * Use negative numbers for the TTL of a request:
time -3! uuid1
time -2 uuid2
The `!` indicates that the request originated on
that node.
* To propigate a request, set -1 * (TTL+1) in the line * To propigate a request, set -1 * (TTL+1) in the line
for the uuid of the repository that is propigating it. for the uuid of the repository that is propigating it.
This should be done as part of the git-annex branch merging, This should be done as part of the git-annex branch merge,
so if a location tracking file is merged, any open requests so if a location tracking file is merged, any open requests
get propigated to the current repository. get propigated to the current repository automatically.
* When a requested file reaches a node that requested it, * When a requested file reaches a node that requested it,
the location is set to 1; this automatically clears the the location is set to 1; this automatically clears the
request. request.
* When a file has no more originating requests, clear all
the copied requests:
time 1 uuid1
time -2 uuid2
Becomes:
time 1 uuid1
time' 0 uuid2
## generating requests ## generating requests

3
doc/devblog/day_163__request_and_routing_design.mdwn Normal file
View file

@ -0,0 +1,3 @@
I have a preliminary design for [[design/requests_routing]]. Won't be
working on it immediately, but simulations show it can work well in a large
ad-hoc network.