[or-cvs] r21398: {projects} update iocp status even more (projects/todo)

[Nick Mathewson <nickm@xxxxxxxxxxxxxx>]

Author: nickm
Date: 2010-01-11 03:39:10 +0000 (Mon, 11 Jan 2010)
New Revision: 21398

Modified:
   projects/todo/TODO.external
Log:
update iocp status even more

Modified: projects/todo/TODO.external
===================================================================
--- projects/todo/TODO.external	2010-01-11 02:02:56 UTC (rev 21397)
+++ projects/todo/TODO.external	2010-01-11 03:39:10 UTC (rev 21398)
@@ -117,16 +117,21 @@
       - Eventually we should fix our stream timeouts too
 
 4.1, IOCP / libevent / windows / tor
-N - get it working for nick
-N - put out a release so other people can start testing it.
-N - both the libevent buffer abstraction, and the
+  - get it working for nick
+    o Port libevent to use IOCP for bufferevents
+    o Port Tor to use bufferevents
+      o Everything else
+      - Rate-limiting
+    o Implement necessar APIs in bufferevents for Tor
+      o OpenSSL
+      o Rate-limiting
+      o Filtering
+    o Test with puppetor for a while
+      . Needs more testing with IOCP, rate-limiting.
+  o both the libevent buffer abstraction, and the
     tor-uses-libevent-buffer-abstraction. Unless we think that's
     unreachable for this milestone?
-    Status: Libevent 2.0.2 came out a few weeks ago. It's a good dev version.
-    Once 2.0.3 is out and there's a Tor alpha in mid Aug that has support
-    for it, we could put out an extra-unstable Tor Windows bundle. Or we
-    might just leave it in the not-quite-finished state for mid-Aug, so we
-    can get microdescriptors going too.
+N - put out a release so other people can start testing it.
 
 4.2.1, risks from becoming a relay
 S - Have a clear plan for how users who become relays will be safe,