[or-cvs] r9245: Initial TODO updates from meeting (in tor/trunk: . doc)

[nickm@xxxxxxxx]

Author: nickm
Date: 2007-01-02 16:47:33 -0500 (Tue, 02 Jan 2007)
New Revision: 9245

Modified:
   tor/trunk/
   tor/trunk/doc/TODO
Log:
 r11801@Kushana:  nickm | 2007-01-02 16:46:54 -0500
 Initial TODO updates from meeting



Property changes on: tor/trunk
___________________________________________________________________
 svk:merge ticket from /tor/trunk [r11801] on c95137ef-5f19-0410-b913-86e773d04f59

Modified: tor/trunk/doc/TODO
===================================================================
--- tor/trunk/doc/TODO	2007-01-02 21:47:28 UTC (rev 9244)
+++ tor/trunk/doc/TODO	2007-01-02 21:47:33 UTC (rev 9245)
@@ -32,14 +32,15 @@
 R - Reconstruct ChangeLog; put rolled-up info in ReleaseNotes or something.
 
 Items for 0.1.2.x:
-  - enumerate events of important things that occur in tor, so vidalia can
+N - enumerate events of important things that occur in tor, so vidalia can
     react.
     o Backend implementation
-R   - Actually list all the events (notice and warn log messages are a good
+R   - Clean up the spec a bit.
+    - Actually list all the events (notice and warn log messages are a good
       place to look.)  Divide messages into categories, perhaps.
-R   - Specify general event system
-R   - Specify actual events.
-R   - and implement the rest
+    - Specify general event system
+    - Specify actual events.
+    - and implement the rest
 
   . Have (and document) a BEGIN_DIR relay cell that means "Connect to your
     directory port."
@@ -133,8 +134,13 @@
     . 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
-      - per-conn write buckets
-      - separate config options for read vs write limiting
+        - Write function to estimate bytes needed for N descriptors
+          statuses
+      D per-conn write buckets
+      D separate config options for read vs write limiting
+        (It's hard to support read > write, since we need better
+         congestion control to avoid overfull buffers there.  So,
+         defer the whole thing.)
 
   - Forward compatibility fixes
     - Caches should start trying to cache consensus docs?