aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2004-11-29 21:01:34 +0000
committerNick Mathewson <nickm@torproject.org>2004-11-29 21:01:34 +0000
commitaff512268563c7c9b0d675a85c7c03bb3ca628ad (patch)
tree6185317b76ea8c90dd23eff73ec589603821d061 /doc
parentb6b07d1d98878cb90aff4cddbcbe860d6b71d285 (diff)
downloadtor-aff512268563c7c9b0d675a85c7c03bb3ca628ad.tar
tor-aff512268563c7c9b0d675a85c7c03bb3ca628ad.tar.gz
Fetch cached running-routers from servers that serve it (that is, authdirservers, and servers running 0.0.9rc5-cvs or later.)
svn:r3018
Diffstat (limited to 'doc')
-rw-r--r--doc/TODO8
1 files changed, 5 insertions, 3 deletions
diff --git a/doc/TODO b/doc/TODO
index 8ddaeaeef..b72612b13 100644
--- a/doc/TODO
+++ b/doc/TODO
@@ -12,12 +12,14 @@ ARMA - arma claims
For 0.0.9:
N&R- bring tor-spec up to date
-N . cache and serve running-routers on other nodes?
- . cache running-routers
- - download running-routers from servers running rc5-cvs or later
+ o cache and serve running-routers on other nodes?
+ o cache running-routers
+ o download running-routers from servers running rc5-cvs or later
N - pump up periods for fetching things; figure out how to do this
backward-compatibily, so that people who did set dirfetchpostperiod
get the right behavior.
+ - If dirport is set, we should have a maximum dirfetchperiod and
+ a maximum statusfetchperiod, or else we'll serve very stale stuff.
N - Adapt version parsing code to handle new version scheme; document new
version scheme.
N&R. make loglevels info,debug less noisy