gzz-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gzz-commits] manuscripts/storm article.rst


From: Hermanni Hyytiälä
Subject: [Gzz-commits] manuscripts/storm article.rst
Date: Mon, 03 Feb 2003 05:01:56 -0500

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Hermanni Hyytiälä <address@hidden>      03/02/03 05:01:54

Modified files:
        storm          : article.rst 

Log message:
        Related work: Lotus Notes & Groove

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/storm/article.rst.diff?tr1=1.75&tr2=1.76&r1=text&r2=text

Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.75 manuscripts/storm/article.rst:1.76
--- manuscripts/storm/article.rst:1.75  Mon Feb  3 04:42:17 2003
+++ manuscripts/storm/article.rst       Mon Feb  3 05:01:54 2003
@@ -122,8 +122,22 @@
 and, at least in its 1988 incarnation [ref Green] addressed data 
 based on the address of a server holding a 'master copy.'
 
+Lotus Notes [ref], popular database sharing and colloboration tool, has some 
+similarities to Storm. In both systems, for instance, data is identified by 
+using GUIDs. However, partly because of the long age of the system, Lotus 
Notes 
+is limited to client-server architecture, where as Storm exploits peer-to-peer 
+architecture. Groove [ref] is a improved design of Lotus Notes, which employs 
+strong security mechanisms and uses peer-to-peer as basis of communication 
+channel among participants. Neither of these systems don't support the 
immutable
+of data.
 
+CFS [ref], which is built upon Chord DHT routing layer[ref], store data as 
blocks. 
+However, CFS *splits* files into several miniblocks and spreads blocks over 
the 
+available CFS servers. Freenet [ref] and PAST [ref, pastry ref] doesn't split 
+files into blocks, since they store data as whole files. All previously 
mentioned 
+systems lack of the immutable property which is used in Storm blocks.
 
+   
 
 
 [Note: The following are my notes for what should be written,
@@ -247,15 +261,6 @@
 byte sequence would change the hash (and thus create a different block).
 Mutable data structures are built on top of the immutable blocks
 (see Section 6).
-
-[Or should these lines be inserted to some other section and tell more about 
these
-systems, e.g. 5.2 ? -Hermanni]
-
-CFS [ref], which is built upon Chord routing layer[ref], store data as blocks. 
-However, CFS *splits* files into several miniblocks and spreads blocks over 
the 
-available CFS servers. Freenet [ref] and PAST [ref, pastry ref] doesn't split 
-files into blocks, since they store data as whole files. All previously 
mentioned 
-systems lack of the immutable property which is used in Storm blocks.
 
 Immutable blocks has several benefits over existing systems...
 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]