Added first monthly status report.
Karsten Loesing commited on 2008-06-16 01:34:50
Zeige 1 geänderte Dateien mit 97 Einfügungen und 2 Löschungen.
- projects/en/hidserv.wml 1f4ddb275..5ddab5790
| ... | ... |
@@ -151,8 +151,103 @@ first deliverable on June 15, 2008 and ending with completion of |
| 151 | 151 |
implementation and testing work on January 15, 2009. |
| 152 | 152 |
</p> |
| 153 | 153 |
|
| 154 |
-<!-- Where do we put status reports? The idea here is to create separate pages. |
|
| 155 |
---> |
|
| 154 |
+<table width="100%" border="0" cellspacing="0" cellpadding="3"> |
|
| 155 |
+<thead> |
|
| 156 |
+<tr> |
|
| 157 |
+<th><big>Month,</big></th> |
|
| 158 |
+<th><big>Status Report</big></th> |
|
| 159 |
+</tr> |
|
| 160 |
+</thead> |
|
| 161 |
+ |
|
| 162 |
+<tr bgcolor="#e5e5e5"> |
|
| 163 |
+ <td> |
|
| 164 |
+ Jun 08 |
|
| 165 |
+ </td> |
|
| 166 |
+ <td> |
|
| 167 |
+ <small><em>The original goal of analyzing the problems that lead to |
|
| 168 |
+ slowdown of Tor Hidden Services has been accomplished. Part of this |
|
| 169 |
+ analysis were measurements of the delay that a user experiences when |
|
| 170 |
+ setting up or accessing a hidden service. Furthermore, measurement data |
|
| 171 |
+ from April 2008 could be leveraged to explore timings of internal |
|
| 172 |
+ substeps of establishing a connection to a hidden service. The results |
|
| 173 |
+ of this analysis are contained in a 22-page |
|
| 174 |
+ <a href="http://freehaven.net/~karsten/hidserv/perfanalysis-2008-06-15.pdf">report</a> |
|
| 175 |
+ that has been made public on the Tor |
|
| 176 |
+ <a href="http://archives.seul.org/or/dev/Jun-2008/msg00019.html">developer |
|
| 177 |
+ mailing list</a>.</small></em> |
|
| 178 |
+ <br/> |
|
| 179 |
+ <small><em>The analysis has unveiled a few bugs which were responsible |
|
| 180 |
+ in parts for the delay in making a hidden service available for |
|
| 181 |
+ clients. Some bugs have been fixed subsequent to the analysis, others |
|
| 182 |
+ will be fixed soon. The evaluation has further brought up several |
|
| 183 |
+ possible approaches to improve Tor Hidden Service performance. Some of |
|
| 184 |
+ these ideas can be applied immediately, while others require deeper |
|
| 185 |
+ analysis and new measurements. Finally, in the course of the analysis, |
|
| 186 |
+ it has been discovered that some improvements require more in-depth |
|
| 187 |
+ changes to Tor which are not directly related to hidden services. These |
|
| 188 |
+ changes cannot be achieved in the time frame of this |
|
| 189 |
+ project.</small></em> |
|
| 190 |
+ </td> |
|
| 191 |
+</tr> |
|
| 192 |
+ |
|
| 193 |
+<tr> |
|
| 194 |
+ <td> |
|
| 195 |
+ Jul 08 |
|
| 196 |
+ </td> |
|
| 197 |
+ <td> |
|
| 198 |
+ </td> |
|
| 199 |
+</tr> |
|
| 200 |
+ |
|
| 201 |
+<tr bgcolor="#e5e5e5"> |
|
| 202 |
+ <td> |
|
| 203 |
+ Aug 08 |
|
| 204 |
+ </td> |
|
| 205 |
+ <td> |
|
| 206 |
+ </td> |
|
| 207 |
+</tr> |
|
| 208 |
+ |
|
| 209 |
+<tr> |
|
| 210 |
+ <td> |
|
| 211 |
+ Sep 08 |
|
| 212 |
+ </td> |
|
| 213 |
+ <td> |
|
| 214 |
+ </td> |
|
| 215 |
+</tr> |
|
| 216 |
+ |
|
| 217 |
+<tr bgcolor="#e5e5e5"> |
|
| 218 |
+ <td> |
|
| 219 |
+ Oct 08 |
|
| 220 |
+ </td> |
|
| 221 |
+ <td> |
|
| 222 |
+ </td> |
|
| 223 |
+</tr> |
|
| 224 |
+ |
|
| 225 |
+<tr> |
|
| 226 |
+ <td> |
|
| 227 |
+ Nov 08 |
|
| 228 |
+ </td> |
|
| 229 |
+ <td> |
|
| 230 |
+ </td> |
|
| 231 |
+</tr> |
|
| 232 |
+ |
|
| 233 |
+<tr bgcolor="#e5e5e5"> |
|
| 234 |
+ <td> |
|
| 235 |
+ Dec 08 |
|
| 236 |
+ </td> |
|
| 237 |
+ <td> |
|
| 238 |
+ </td> |
|
| 239 |
+</tr> |
|
| 240 |
+ |
|
| 241 |
+<tr> |
|
| 242 |
+ <td> |
|
| 243 |
+ Jan 09 |
|
| 244 |
+ </td> |
|
| 245 |
+ <td> |
|
| 246 |
+ </td> |
|
| 247 |
+</tr> |
|
| 248 |
+</table> |
|
| 249 |
+ |
|
| 250 |
+<br /> |
|
| 156 | 251 |
|
| 157 | 252 |
<!-- Do we want a people section? If so, would it make sense to write what |
| 158 | 253 |
these people will be doing? And---what exactly are these people going to |
| 159 | 254 |