gzz-commits
[Top][All Lists]
Advanced

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

[Gzz-commits] gzz/Documentation/misc/hemppah-progradu mastert...


From: Hermanni Hyytiälä
Subject: [Gzz-commits] gzz/Documentation/misc/hemppah-progradu mastert...
Date: Tue, 25 Mar 2003 09:57:30 -0500

CVSROOT:        /cvsroot/gzz
Module name:    gzz
Changes by:     Hermanni Hyytiälä <address@hidden>      03/03/25 09:57:30

Modified files:
        Documentation/misc/hemppah-progradu: masterthesis.tex 

Log message:
        Clarify

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/gzz/Documentation/misc/hemppah-progradu/masterthesis.tex.diff?tr1=1.188&tr2=1.189&r1=text&r2=text

Patches:
Index: gzz/Documentation/misc/hemppah-progradu/masterthesis.tex
diff -u gzz/Documentation/misc/hemppah-progradu/masterthesis.tex:1.188 
gzz/Documentation/misc/hemppah-progradu/masterthesis.tex:1.189
--- gzz/Documentation/misc/hemppah-progradu/masterthesis.tex:1.188      Tue Mar 
25 09:23:59 2003
+++ gzz/Documentation/misc/hemppah-progradu/masterthesis.tex    Tue Mar 25 
09:57:30 2003
@@ -1681,7 +1681,10 @@
 see \cite{lukka02freenetguids}, and for detailed Storm design, see 
\cite{fallenstein03storm}.
 
 Storm (for \emph{STORage Module}) stores all data as \emph{blocks}, which
-are immutable byte sequences. SHA-1 cryptographic content hash 
function\footnote{SHA-1 is 
+are immutable byte sequences. Storm \emph{assigns} a globally unique 
identifier to each
+data block\footnote{This resembles the process how tightly structured overlay 
assigns a subset of keys
+to each participating peer: a user has no control over the assignment 
process.}. SHA-1 cryptographic 
+content hash function\footnote{SHA-1 is 
 considered as a collision free hash function. Therefore, it is very unlikely 
that two different Storm data blocks 
 would have same identifier.} \cite{fips-sha-1} is used
 for creating location-independent, globally unique identifiers for blocks. 
Because of SHA-1
@@ -1801,7 +1804,8 @@
 For Fenfire's needs for \emph{locating} data, an important advantage of the 
 tightly structured approach over the loosely structured approach is that both 
tightly 
 structured systems and Fenfire use similar methods for identifying data in the
-system, i.e., globally unique identifiers.
+system, i.e., Storm provides globally unique identifiers which can be used in 
the
+tightly structured overlay.
 Another key feature of tightly structured overlays is that they are able
 to provide general purpose \emph{interface} for Reference Resolution Services 
(RRS)
  \cite{balakrishnan03semanticfree}. Authors argue that next generation RRS 
must be 




reply via email to

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