[Gzz-commits] storm/doc/pegboard/available_overlays--hemppah ...

[Hermanni Hyytiälä]

CVSROOT:        /cvsroot/storm
Module name:    storm
Branch:         
Changes by:     Hermanni Hyytiälä <address@hidden>      03/07/28 08:58:11

Modified files:
        doc/pegboard/available_overlays--hemppah: peg.rst 

Log message:
        better conclusions

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/storm/storm/doc/pegboard/available_overlays--hemppah/peg.rst.diff?tr1=1.33&tr2=1.34&r1=text&r2=text

Patches:
Index: storm/doc/pegboard/available_overlays--hemppah/peg.rst
diff -u storm/doc/pegboard/available_overlays--hemppah/peg.rst:1.33 
storm/doc/pegboard/available_overlays--hemppah/peg.rst:1.34
--- storm/doc/pegboard/available_overlays--hemppah/peg.rst:1.33 Mon Jul 28 
08:39:14 2003
+++ storm/doc/pegboard/available_overlays--hemppah/peg.rst      Mon Jul 28 
08:58:11 2003
@@ -4,8 +4,8 @@
 
 :Authors:  Hermanni Hyytiälä
 :Date-Created: 2003-06-18
-:Last-Modified: $Date: 2003/07/28 12:39:14 $
-:Revision: $Revision: 1.33 $
+:Last-Modified: $Date: 2003/07/28 12:58:11 $
+:Revision: $Revision: 1.34 $
 :Status:   Incomplete
 
 .. :Stakeholders:
@@ -18,9 +18,8 @@
 P2P overlays which have an open source implementation. 
 
 The reason for creating this PEG document is that the current implementation 
-of GISP [5]_ seems to have (too) many obvious security exploits. For us this 
-indiciates that GISP is in early phase of development. Therefore we need to 
-examine other available structured overlays which have an open source 
+of GISP [5]_ seems to have (too) many obvious security exploits. Therefore we 
need 
+to examine other available structured overlays which have an open source 
 implementation in hope for finding a more mature P2P platform. 
 
 The list of implemented overlays is as of July 2003.
@@ -30,10 +29,10 @@
 
 None.
 
-Terms
-=====
+Terminology
+===========
 
-This section briefly covers the terms used in this document. 
+This section briefly covers the terminology used in this document. 
 
 Abstractions
     The following text for the abstraction definitions is taken from 
@@ -72,11 +71,10 @@
         to the underlying nodes or links.
 
 Redundancy
-    How well overlay handles 'normal' failures (nodes or connections fail 
-    randomly).
+    What techniques are used for redundancy     
 
 Fault tolerance against hostile nodes
-    How well overlay handles failures which are caused by a hostile node(s).
+    What techniques are used against hostile nodes    
 
 Activity of development
     How actively a software is being developed.
@@ -309,15 +307,14 @@
    Backup links.
 
 Fault tolerance against hostile nodes
-   Accordin to the release notes of 1.2, "Security support does not exist in 
+   According to the release notes of 1.2, "Security support does not exist in 
     this release. Therefore, the  software should only be run in trusted 
     environments. Future releases will include security."
 
 Activity of development
     Active
     
-    Current release is 1.3 (July 23, 2003)
-    
+    Current release is 1.3 (July 23, 2003), no release notes available for 1.3 
yet    
 
 Developer
     Microsoft Research and Rice University (research community)
@@ -352,8 +349,8 @@
     Chord [1]_-like (since GISP uses similar routing tables as Chord)
 
 Fault tolerance against hostile nodes
-    Based on our own initial experiments, the fault tolerance
-    is relatively weak.
+    Based on our own initial experiments: the fault tolerance
+    is relatively weak - no specific techiques used.
 
 Activity of development
     Quite active.
@@ -385,7 +382,7 @@
     According to Info-Anarchy Wiki:
 
         Problems are: The DHT implementation is 
-        vulnerable to denial of service attacks.
+        vulnerable to denial of service attacks.    
 
 Activity of development
     Active, the current version is 0.35 (30 May 2003)
@@ -445,10 +442,12 @@
     Kademlia [3]_ and multisource downloading)
 
 Redundancy
-    Not known
+    Not known (we can imagine that redundancy is relatively high since MLDonkey
+    is widely deplyed)
 
 Fault tolerance against hostile nodes
-    Not known
+    Not known (we can imagine that fault tolerance is relatively high since 
MLDonkey
+    is widely deplyed)
 
 Activity of development
     Very active
@@ -505,7 +504,7 @@
         several months now. Stable."
 
 Fault tolerance against hostile nodes
-    (undefined)
+    No specific techniques used: "it should work as is"
 
 Activity of development
     The current version is 0.2b3 (16th February 2003)
@@ -591,14 +590,16 @@
 
 While reviewing the different features of open source implementations of 
 structured P2P overlays we can conclude that Tapestry seems to be the most
-mature currently available. Thus we recommend using Tapestry's open source 
-implementation with Storm. Other reasons for choosing Tapestry in order of 
+mature currently available. Specifically, other implementations
+lack of features w.r.t. redundancy and fault tolerance that the Tapestry
+implementation currently supports. Other reasons for choosing Tapestry in 
order of 
 importance:
 
 - The license
 - The activity of development
 - The implementation language
 
+As a result, we recommend using Tapestry's open source implementation with 
Storm.
 For detailed changes and information about using Tapestry with Storm, please
 see the `storm_with_tapestry--hemppah` PEG document.