aboutsummaryrefslogtreecommitdiff
path: root/doc/TODO
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2007-01-03 19:58:00 +0000
committerNick Mathewson <nickm@torproject.org>2007-01-03 19:58:00 +0000
commit2963d4acc267102e1b2927ed6bbcd0717fbae67e (patch)
tree25a7b9091ce8e207624c040a507ffbf835b0f97a /doc/TODO
parent931e555ef9c3d1ec88d1f051cb01c4d09e608876 (diff)
downloadtor-2963d4acc267102e1b2927ed6bbcd0717fbae67e.tar
tor-2963d4acc267102e1b2927ed6bbcd0717fbae67e.tar.gz
r11820@Kushana: nickm | 2007-01-03 14:54:05 -0500
Add (and specify) a BadDirectory flag to networkstatuses, so authorities can tell clients that some caches are broken. Also, implement an as-yet-unused function to estimate how many bytes will be sent on a directory connection. svn:r9255
Diffstat (limited to 'doc/TODO')
-rw-r--r--doc/TODO6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/TODO b/doc/TODO
index fc1b36352..7aa67bd39 100644
--- a/doc/TODO
+++ b/doc/TODO
@@ -86,7 +86,7 @@ N - DNS improvements
D But eventually, we give up after getting a lot of 503s.
D Delay when we get a lot of 503s, rather than punting onto the
servers that have given us 503s?
-N - Add a 'BadDirectory' flag to statuses.
+ o Add a 'BadDirectory' flag to statuses.
- authorities should *never* 503 a cache, and should never 503
network status requests. They can 503 client descriptor requests
when they feel like it.
@@ -136,8 +136,8 @@ R - "bandwidth classes", for incoming vs initiated-here conns,
and to give dir conns lower priority.
. Write limiting; separate token bucket for write
o preemptively give a 503 to some v1 dir requests
- - preemptively give a 503 to some v2 dir requests
- - Write function to estimate bytes needed for N descriptors
+R - preemptively give a 503 to some v2 dir requests
+ o Write function to estimate bytes needed for N descriptors
statuses
D per-conn write buckets
D separate config options for read vs write limiting