summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2006-04-03 05:51:18 +0000
committerNick Mathewson <nickm@torproject.org>2006-04-03 05:51:18 +0000
commit1f40ab57d75aa60386067d567b80a48c0ea03063 (patch)
treefecec7cb9d45f19621b03f564de9c4ef5cec90e2 /doc
parentefcc4d75954d47fee82985daa879863e599e03dd (diff)
downloadtor-1f40ab57d75aa60386067d567b80a48c0ea03063.tar.gz
tor-1f40ab57d75aa60386067d567b80a48c0ea03063.zip
Oops; meant received, not published.
svn:r6304
Diffstat (limited to 'doc')
-rw-r--r--doc/dir-spec.txt10
1 files changed, 6 insertions, 4 deletions
diff --git a/doc/dir-spec.txt b/doc/dir-spec.txt
index 0ef3eea5e8..68d9bc1118 100644
--- a/doc/dir-spec.txt
+++ b/doc/dir-spec.txt
@@ -394,8 +394,10 @@ $Id$
Each client maintains an ordered list of directory authorities.
Insofar as possible, clients SHOULD all use the same ordered list.
- Clients consider a network-status document "live" if it was published
- within the last 24 hours.
+ For each network-status document a client has, it keeps track of its
+ publication time *and* the time when the client retrieved it. Clients
+ consider a network-status document "live" if it was published within the
+ last 24 hours.
Clients try to have a live network-status document hours from *every*
authority, and try to periodically get new network-status documents from
@@ -408,12 +410,12 @@ $Id$
has a live network-status document, or until is has tried and failed to
get a network-status document.
- Also, if the most recently published network-status document is over 30
+ If the most recently _retrieved_ network-status document is over 30
minutes old, the client attempts to download a network-status document.
When choosing which documents to download, clients treat their list of
directory authorities as a circular ring, and begin with the authority
appearing immediately after the authority for their most recently
- published network-status document. If this attempt fails, the client
+ retrieved network-status document. If this attempt fails, the client
retries at other caches several times, before moving on to the next
network-status document in sequence.