[or-cvs] Move some TODO items out of the 0.1.0.1-rc pile

Nick Mathewson nickm at seul.org
Thu Mar 24 01:12:40 UTC 2005


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

Modified Files:
	TODO 
Log Message:
Move some TODO items out of the 0.1.0.1-rc pile

Index: TODO
===================================================================
RCS file: /home/or/cvsroot/tor/doc/TODO,v
retrieving revision 1.293
retrieving revision 1.294
diff -u -d -r1.293 -r1.294
--- TODO	23 Mar 2005 19:15:09 -0000	1.293
+++ TODO	24 Mar 2005 01:12:38 -0000	1.294
@@ -24,8 +24,6 @@
      haven't made a circ yet.
    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?
    o have a separate config option which caps bandwidth-to-advertise.
    o Make list_server_status work right on non-directories, so that 
      getinfo("network-status") control message can work there.
@@ -161,6 +159,10 @@
 R    - should retry exitpolicy end streams even if the end cell didn't
        resolve the address for you
    o Figure out when to reset addressmaps (on hup, on reconfig, etc)
+   - how do ulimits work on win32, anyway?  (We should handle WSAENOBUFS as
+     needed, look at the MaxConnections registry entry, look at the
+     MaxUserPort entry, and look at the TcpTimedWaitDelay entry. We may also
+     want to provide a way to set them as needed. See bug 98.)
 
  Improvements to self-measurement.
 R  X round detected bandwidth up to nearest 10KB?
@@ -202,6 +204,7 @@
     - Investigate hidden service performance/reliability
   - Add private:* alias in exit policies to make it easier to ban all the
     fiddly little 192.168.foo addresses.
+  - controller should have an event to learn about new addressmappings?
 
 
   No



More information about the tor-commits mailing list