14 |
|
|
15 |
.. Affect-PEGs: |
.. Affect-PEGs: |
16 |
|
|
17 |
The purpose of this PEG document is to give a short overview of existing |
The purpose of this PEG document is to give a short overview of existing structured |
18 |
overlays which have an open source implementation. |
P2P overlays which have an open source implementation. |
19 |
|
|
20 |
The reason for creating this PEG document is that the current implementation |
The reason for creating this PEG document is that the current implementation |
21 |
of GISP [5]_ seems to have (too) many obvious security exploits. For us this |
of GISP [5]_ seems to have (too) many obvious security exploits. For us this |
22 |
indiciates that GISP is in early phase of development. Therefore we need to |
indiciates that GISP is in early phase of development. Therefore we need to |
23 |
examine other available overlays which have an implementation in hope for |
examine other available structured overlays which have an open source |
24 |
finding a more mature tightly structured P2P platform. |
implementation in hope for finding a more mature P2P platform. |
25 |
|
|
26 |
The list of implemented overlays is as of July 2003. |
The list of implemented overlays is as of July 2003. |
27 |
|
|
97 |
Implemented overlays |
Implemented overlays |
98 |
==================== |
==================== |
99 |
|
|
100 |
In this section we list the structured P2P overlays which have been implemented. |
In this section we list the structured P2P overlays which have an open source |
101 |
Please notice that features described for each implementation are deliberately |
implementation. Please notice that features described for each implementation |
102 |
kept short. For more depth information about the *design* of the overlay see |
are deliberately kept as short as possible. For more depth information about the |
103 |
the original publications. |
*planned features* of the overlays we suggest reading the original publications. |
104 |
|
|
105 |
Chord [1]_ |
Chord [1]_ |
106 |
---------- |
---------- |
139 |
BSD-like |
BSD-like |
140 |
|
|
141 |
Other notes |
Other notes |
142 |
No support for network locality- do not take network latencies into account. |
No support for network locality- do not take network latencies into account |
143 |
|
when building neighbor links. |
144 |
|
|
145 |
Includes a Chord [1]_ simulator. |
Includes a Chord [1]_ simulator. |
146 |
|
|
236 |
|
|
237 |
Language |
Language |
238 |
Java (Sun JDK 1.3 or a compatible Java Development and Runtime environment). |
Java (Sun JDK 1.3 or a compatible Java Development and Runtime environment). |
239 |
The Java interface libraries for the BerkeleyDB database (included with this |
The Java interface libraries for the BerkeleyDB database |
|
release). |
|
240 |
|
|
241 |
Additional requirements |
Additional requirements |
242 |
* The Cryptix JCE library (included with the 2.0 release) |
* The Cryptix JCE library (included with the 2.0 release) |
317 |
Active |
Active |
318 |
|
|
319 |
Current release is 1.3 (July 23, 2003) |
Current release is 1.3 (July 23, 2003) |
320 |
|
|
|
According to the Pastry [4]_ website: |
|
|
|
|
|
"Future releases will address efficiency, |
|
|
security, interoperability and will provide additional |
|
|
application components like a generic distributed |
|
|
hash table implementation, replica management, |
|
|
caching, etc." |
|
321 |
|
|
322 |
Developer |
Developer |
323 |
Microsoft Research and Rice University (research community) |
Microsoft Research and Rice University (research community) |
332 |
Support for network locality - Pastry [4]_ actively replicates the objects and |
Support for network locality - Pastry [4]_ actively replicates the objects and |
333 |
places them at random locations in the network. Result: When locating |
places them at random locations in the network. Result: When locating |
334 |
nearby object it might require the client to route to a distant replica of |
nearby object it might require the client to route to a distant replica of |
335 |
the object. |
the object. |
336 |
|
|
337 |
|
According to the Pastry [4]_ website: |
338 |
|
|
339 |
|
Future releases will address efficiency, |
340 |
|
security, interoperability and will provide additional |
341 |
|
application components like a generic distributed |
342 |
|
hash table implementation, replica management, |
343 |
|
caching, etc. |
344 |
|
|
345 |
GISP [5]_ |
GISP [5]_ |
346 |
--------- |
--------- |
349 |
DHT_/DOLR_ |
DHT_/DOLR_ |
350 |
|
|
351 |
Redundancy |
Redundancy |
352 |
Chord [1]_-like. |
Chord [1]_-like (since GISP uses similar routing tables as Chord) |
353 |
|
|
354 |
Fault tolerance against hostile nodes |
Fault tolerance against hostile nodes |
355 |
Based on our initial experiments, the fault tolerance |
Based on our own initial experiments, the fault tolerance |
356 |
is relatively weak. |
is relatively weak. |
357 |
|
|
358 |
Activity of development |
Activity of development |
569 |
should send any bugreports to me. |
should send any bugreports to me. |
570 |
|
|
571 |
Developer |
Developer |
572 |
Sprachenzentrum der Universität des Saarlandes / Heiko Wundram (software |
Sprachenzentrum der Universität des Saarlandes / Heiko Wundram (research community) |
|
engineering community) |
|
573 |
|
|
574 |
Language |
Language |
575 |
Python |
Python |