[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gzz-commits] storm/doc/pegboard/available_overlays--hemppah ...
From: |
Hermanni Hyytiälä |
Subject: |
[Gzz-commits] storm/doc/pegboard/available_overlays--hemppah ... |
Date: |
Mon, 28 Jul 2003 05:10:56 -0400 |
CVSROOT: /cvsroot/storm
Module name: storm
Branch:
Changes by: Hermanni Hyytiälä <address@hidden> 03/07/28 05:10:56
Modified files:
doc/pegboard/available_overlays--hemppah: peg.rst
Log message:
updates
CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/storm/storm/doc/pegboard/available_overlays--hemppah/peg.rst.diff?tr1=1.28&tr2=1.29&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.28
storm/doc/pegboard/available_overlays--hemppah/peg.rst:1.29
--- storm/doc/pegboard/available_overlays--hemppah/peg.rst:1.28 Mon Jul 21
14:04:40 2003
+++ storm/doc/pegboard/available_overlays--hemppah/peg.rst Mon Jul 28
05:10:55 2003
@@ -4,8 +4,8 @@
:Authors: Hermanni Hyytiälä
:Date-Created: 2003-06-18
-:Last-Modified: $Date: 2003/07/21 18:04:40 $
-:Revision: $Revision: 1.28 $
+:Last-Modified: $Date: 2003/07/28 09:10:55 $
+:Revision: $Revision: 1.29 $
:Status: Incomplete
.. :Stakeholders:
@@ -14,15 +14,15 @@
.. Affect-PEGs:
-The purpose of this PEG document is to give short overview of existing
-overlays which have an implementation and try to choose the implementation
-which suits best to our needs.
+The purpose of this PEG document is to give a short overview of existing
+overlays which have an implementation and try to choose an implementation
+that suits best to our needs.
The reason for creating this PEG document is that, quite recently, we have
noticed that the current implementation of GISP [5]_ seems to
-have many obvious security exploits. This indiciates that GISP is in early
+have (too) many obvious security exploits. This indiciates that GISP is in
early
phase of development. Therefore, we need to examine other
-available overlays which have a implementation in hope for finding a more
+available overlays which have an implementation in hope for finding a more
mature tightly structured P2P platform.
The list of implemented overlays is of as of June 2003.
@@ -30,8 +30,7 @@
Issues
======
-How "heavy" the current implementation of Tapestry is (~57000 lines of
-Java code)? And therefore, does Tapestry consume too much memory?
+.. nothing yet.
Terms
=====
@@ -91,7 +90,7 @@
What programming language is used to program a software.
License
- Which license is used with a software.
+ Under what license a software is distributed.
Other notes
Other miscellaneous notes.
@@ -126,7 +125,7 @@
C++ (GCC 2.95, not 2.96, although 3.x should work)
Additional requirements
- * Self-certifying File System (http://fs.net)
+ * Self-certifying File System (http://sfs.net)
* autoconf, automake, etc.
* Berkeley DB 3.X
@@ -134,16 +133,16 @@
BSD-like
Other notes
- No support for network locality- do not take network latencies into account
+ No support for network locality- do not take network latencies into
account.
- Includes a Chord [1]_ simulator
+ Includes a Chord [1]_ simulator.
According to the Chord [1]_ website:
- "At this point no official release for
+ At this point no official release for
Chord is available, but you are welcome to check out the latest
version
from the CVS repository. This version is experimental, under active
- development, and may frequently be broken."
+ development, and may frequently be broken.
Tapestry [2]_
--------------
@@ -155,10 +154,10 @@
According to `Tapestry: A Resilient Global-scale Overlay for Service
Deployment`_:
- "Tapestry is highly resilient under dynamic conditions,
+ Tapestry is highly resilient under dynamic conditions,
providing a near optimal success rate for requests
under high churn rates, and quicly recovering from
- massive membership events in under a minute."
+ massive membership events in under a minute.
According to the Tapestry [2]_ website:
@@ -179,8 +178,9 @@
Replication, backup links
Fault tolerance against hostile nodes
- * PKI is used while creating node identifiers.
- * MACs are used to maintain integrity of overlay traffic.
+ * PKI is used while creating node identifiers
+ * MACs are used to maintain integrity of overlay traffic
+ * Monitoring system for maintaining neighbor links
Activity of development
Very active.
@@ -280,10 +280,10 @@
Activity of development
Java development discontinued, C++ version
- is under development
+ is under development.
Developer
- New York University (research community)
+ New York University (research community).
Language
Java (Sun JDK 1.3 or a compatible Java Development and Runtime environment
(?))
@@ -301,7 +301,7 @@
DHT_/DOLR_
Redundancy
- (undefined)
+ Backup links.
Fault tolerance against hostile nodes
(undefined)
@@ -346,11 +346,11 @@
Chord [1]_-like.
Fault tolerance against hostile nodes
- Weak (the current implementation), not known
- (the current protocol specification)
+ Based on our initial experiments, the fault tolerance
+ is relatively weak.
Activity of development
- (undefined)
+ Quite active.
Developer
Daishi Kato (software engineering community)
@@ -362,9 +362,9 @@
Sun Project JXTA License Version 1.1
Other notes
- Uses 10x more cache as Chord [1]_ for routing table
+ Uses 10x more cache as Chord [1]_ for routing table.
- Includes a GISP [5]_ simulator
+ Includes a GISP [5]_ simulator.
Circle [6]_
-----------
@@ -395,8 +395,8 @@
According to Info-Anarchy Wiki:
- "Problems are: The DHT implementation is
- vulnerable to denial of service attacks."
+ Problems are: The DHT implementation is
+ vulnerable to denial of service attacks.
Khashmir [7]_
-------------
@@ -410,11 +410,11 @@
Fault tolerance against hostile nodes
According to the authors:
- "Note that Khashmir currently isn't very
- attack resistant."
+ Note that Khashmir currently isn't very
+ attack resistant.
Activity of development
- Not active (?)
+ Not active
The current version is "3 - Alpha" (2002-09-02)
@@ -579,9 +579,15 @@
Changes
=======
-- (possible) reject gisp, choose new overlay
-- (possible) develop a abstraction (i.e., p2p-plugin system) which allows
- Storm to change lookup layer easily
+Based on this PEG document we recommend using Tapestry [2]_ with Storm. The
+reasons are:
+
+- maturity of the implementation (the most important aspect)
+- activity of development
+- the license
+
+
+
.. [1] http://www.pdos.lcs.mit.edu/chord/
.. [2] http://www.cs.berkeley.edu/~ravenben/tapestry/
- [Gzz-commits] storm/doc/pegboard/available_overlays--hemppah ..., Hermanni Hyytiälä, 2003/07/03
- [Gzz-commits] storm/doc/pegboard/available_overlays--hemppah ..., Hermanni Hyytiälä, 2003/07/09
- [Gzz-commits] storm/doc/pegboard/available_overlays--hemppah ..., Hermanni Hyytiälä, 2003/07/09
- [Gzz-commits] storm/doc/pegboard/available_overlays--hemppah ..., Hermanni Hyytiälä, 2003/07/09
- [Gzz-commits] storm/doc/pegboard/available_overlays--hemppah ..., Hermanni Hyytiälä, 2003/07/09
- [Gzz-commits] storm/doc/pegboard/available_overlays--hemppah ..., Asko Soukka, 2003/07/21
- [Gzz-commits] storm/doc/pegboard/available_overlays--hemppah ...,
Hermanni Hyytiälä <=
- [Gzz-commits] storm/doc/pegboard/available_overlays--hemppah ..., Hermanni Hyytiälä, 2003/07/28
- [Gzz-commits] storm/doc/pegboard/available_overlays--hemppah ..., Hermanni Hyytiälä, 2003/07/28
- [Gzz-commits] storm/doc/pegboard/available_overlays--hemppah ..., Hermanni Hyytiälä, 2003/07/28
- [Gzz-commits] storm/doc/pegboard/available_overlays--hemppah ..., Hermanni Hyytiälä, 2003/07/28
- [Gzz-commits] storm/doc/pegboard/available_overlays--hemppah ..., Hermanni Hyytiälä, 2003/07/28
- [Gzz-commits] storm/doc/pegboard/available_overlays--hemppah ..., Hermanni Hyytiälä, 2003/07/28
- [Gzz-commits] storm/doc/pegboard/available_overlays--hemppah ..., Hermanni Hyytiälä, 2003/07/29
- [Gzz-commits] storm/doc/pegboard/available_overlays--hemppah ..., Hermanni Hyytiälä, 2003/07/29
- [Gzz-commits] storm/doc/pegboard/available_overlays--hemppah ..., Hermanni Hyytiälä, 2003/07/29
- [Gzz-commits] storm/doc/pegboard/available_overlays--hemppah ..., Hermanni Hyytiälä, 2003/07/31