[or-cvs] Report HTTP reasons to directory clients. (Also, fix format...

Nick Mathewson nickm at seul.org
Tue Mar 22 18:43:27 UTC 2005


Update of /home/or/cvsroot/tor/doc
In directory moria.mit.edu:/tmp/cvs-serv20714/doc

Modified Files:
	TODO 
Log Message:
Report HTTP reasons to directory clients. (Also, fix format on new TODO items)

Index: TODO
===================================================================
RCS file: /home/or/cvsroot/tor/doc/TODO,v
retrieving revision 1.288
retrieving revision 1.289
diff -u -d -r1.288 -r1.289
--- TODO	22 Mar 2005 05:19:44 -0000	1.288
+++ TODO	22 Mar 2005 18:43:24 -0000	1.289
@@ -21,12 +21,11 @@
    o finish messing with reachability stuff
    o if we jump in time a lot, then mark our circs and note that we
      haven't made a circ yet.
-
-actually give http reason phrases to dir clients, so they know why
-  they're rejected.
-controller should have an event to learn about new addressmappings?
-how do ulimits work on win32, anyway?
-have a separate config option which caps bandwidth-to-advertise.
+   o actually give http reason phrases to dir clients, so they know why
+     they're rejected.
+   - controller should have an event to learn about new addressmappings?
+   - how do ulimits work on win32, anyway?
+   - have a separate config option which caps bandwidth-to-advertise.
 
 For 0.1.0.x:
 
@@ -97,6 +96,7 @@
       o Time out never-attached streams.
       o If we never get a CONNECTED back, we should put the stream back in
         CONTROLLER_WAIT, not in CIRCUIT_WAIT.
+      - Add a way for the controller to say, "Hey, nuke this stream."
     - Tests for new controller features
 R o HTTPS proxy for OR CONNECT stuff. (For outgoing SSL connections to
     other ORs.)



More information about the tor-commits mailing list