[or-cvs] r15290: Added first monthly status report. (website/trunk/projects/en)
kloesing at seul.org
kloesing at seul.org
Sun Jun 15 23:34:50 UTC 2008
Author: kloesing
Date: 2008-06-15 19:34:50 -0400 (Sun, 15 Jun 2008)
New Revision: 15290
Modified:
website/trunk/projects/en/hidserv.wml
Log:
Added first monthly status report.
Modified: website/trunk/projects/en/hidserv.wml
===================================================================
--- website/trunk/projects/en/hidserv.wml 2008-06-15 23:06:39 UTC (rev 15289)
+++ website/trunk/projects/en/hidserv.wml 2008-06-15 23:34:50 UTC (rev 15290)
@@ -151,9 +151,104 @@
implementation and testing work on January 15, 2009.
</p>
-<!-- Where do we put status reports? The idea here is to create separate pages.
--->
+<table width="100%" border="0" cellspacing="0" cellpadding="3">
+<thead>
+<tr>
+<th><big>Month,</big></th>
+<th><big>Status Report</big></th>
+</tr>
+</thead>
+<tr bgcolor="#e5e5e5">
+ <td>
+ Jun 08
+ </td>
+ <td>
+ <small><em>The original goal of analyzing the problems that lead to
+ slowdown of Tor Hidden Services has been accomplished. Part of this
+ analysis were measurements of the delay that a user experiences when
+ setting up or accessing a hidden service. Furthermore, measurement data
+ from April 2008 could be leveraged to explore timings of internal
+ substeps of establishing a connection to a hidden service. The results
+ of this analysis are contained in a 22-page
+ <a href="http://freehaven.net/~karsten/hidserv/perfanalysis-2008-06-15.pdf">report</a>
+ that has been made public on the Tor
+ <a href="http://archives.seul.org/or/dev/Jun-2008/msg00019.html">developer
+ mailing list</a>.</small></em>
+ <br/>
+ <small><em>The analysis has unveiled a few bugs which were responsible
+ in parts for the delay in making a hidden service available for
+ clients. Some bugs have been fixed subsequent to the analysis, others
+ will be fixed soon. The evaluation has further brought up several
+ possible approaches to improve Tor Hidden Service performance. Some of
+ these ideas can be applied immediately, while others require deeper
+ analysis and new measurements. Finally, in the course of the analysis,
+ it has been discovered that some improvements require more in-depth
+ changes to Tor which are not directly related to hidden services. These
+ changes cannot be achieved in the time frame of this
+ project.</small></em>
+ </td>
+</tr>
+
+<tr>
+ <td>
+ Jul 08
+ </td>
+ <td>
+ </td>
+</tr>
+
+<tr bgcolor="#e5e5e5">
+ <td>
+ Aug 08
+ </td>
+ <td>
+ </td>
+</tr>
+
+<tr>
+ <td>
+ Sep 08
+ </td>
+ <td>
+ </td>
+</tr>
+
+<tr bgcolor="#e5e5e5">
+ <td>
+ Oct 08
+ </td>
+ <td>
+ </td>
+</tr>
+
+<tr>
+ <td>
+ Nov 08
+ </td>
+ <td>
+ </td>
+</tr>
+
+<tr bgcolor="#e5e5e5">
+ <td>
+ Dec 08
+ </td>
+ <td>
+ </td>
+</tr>
+
+<tr>
+ <td>
+ Jan 09
+ </td>
+ <td>
+ </td>
+</tr>
+</table>
+
+<br />
+
<!-- Do we want a people section? If so, would it make sense to write what
these people will be doing? And---what exactly are these people going to
do? :)
More information about the tor-commits
mailing list