[or-cvs] r17114: {website} Monthly status report for October. (website/trunk/projects/en)

[kloesing at seul.org]

Author: kloesing
Date: 2008-10-15 19:01:29 -0400 (Wed, 15 Oct 2008)
New Revision: 17114

Modified:
   website/trunk/projects/en/hidserv.wml
Log:
Monthly status report for October.

Modified: website/trunk/projects/en/hidserv.wml
===================================================================
--- website/trunk/projects/en/hidserv.wml	2008-10-15 22:01:17 UTC (rev 17113)
+++ website/trunk/projects/en/hidserv.wml	2008-10-15 23:01:29 UTC (rev 17114)
@@ -275,9 +275,28 @@
 
 <tr bgcolor="#e5e5e5">
   <td>
-    Oct 08
+    <a id="Oct 08"></a>
+    <a class="anchor" href="#Oct08">Oct 08</a>
   </td>
   <td>
+    <small><em>The implementation phase has been concluded. The bugfixes
+    that were found in the past 30 days have been released in developer
+    version <a href="http://archives.seul.org/or/talk/Oct-2008/msg00093.html">0.2.1.6-alpha</a>.
+    The four design changes that were identified in the design phase have
+    been specified in
+    <a href="https://tor-svn.freehaven.net/svn/tor/trunk/doc/spec/proposals/155-four-hidden-service-improvements.txt">proposal 155</a>.
+    Three design changes have been included in the development codebase and
+    will automatically be included in the next development version. The
+    first two design changes improve connection establishment to a hidden
+    service by reducing a timeout from 60 to 30 seconds and by making a
+    second attempt in parallel after a delay of 15 seconds. The third
+    design change affects publication of a hidden service in the network by
+    advertising the service at 5 rather than 3 points in the network in
+    parallel and succeed as soon as 3 points are established. The fourth
+    design change has turned out to be rather ineffective, but would add
+    considerable code complexity and was therefore dismissed. By now there
+    are no more open bugfixes or new designs. All changes are in the
+    development codebase and can be tested in the next phase.</em></small>
   </td>
 </tr>