[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[or-cvs] r9844: mention torflow as a fine thing to work on (website/trunk/en)

Author: arma
Date: 2007-03-16 05:42:17 -0400 (Fri, 16 Mar 2007)
New Revision: 9844

mention torflow as a fine thing to work on

Modified: website/trunk/en/volunteer.wml
--- website/trunk/en/volunteer.wml	2007-03-16 07:11:35 UTC (rev 9843)
+++ website/trunk/en/volunteer.wml	2007-03-16 09:42:17 UTC (rev 9844)
@@ -115,9 +115,10 @@
 that a medium sized Tor server will empty the non-page pool, <a
 havoc and system crashes</a>. We should probably be using overlapped IO
-instead. One solution would be to teach libevent how to use overlapped IO
-rather than select() on Windows, and then adapt Tor to the new libevent
+instead. One solution would be to teach <a
+href="http://www.monkey.org/~provos/libevent/";>libevent</a> how to use
+overlapped IO rather than select() on Windows, and then adapt Tor to
+the new libevent interface.</li>
 <li>Because Tor servers need to store-and-forward each cell they handle,
 high-bandwidth Tor servers end up using dozens of megabytes of memory
 just for buffers. We need better heuristics for when to shrink/expand
@@ -177,6 +178,12 @@
 <li>We need a distributed testing framework. We have unit tests,
 but it would be great to have a script that starts up a Tor network, uses
 it for a while, and verifies that at least parts of it are working.</li>
+<li>Help Mike Perry on his <a
+library: it's a python library that uses the <a
+href="http://tor.eff.org/svn/torctl/doc/howto.txt";>Tor controller
+protocol</a> to instruct Tor to build circuits in a variety of ways,
+and then it measures performance and tries to detect anomalies.</li>
 <li>Right now the hidden service descriptors are being stored on just a
 few directory servers. This is bad for privacy and bad for robustness. To