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

[Hermanni Hyytiälä]

CVSROOT:        /cvsroot/gzz
Module name:    gzz
Changes by:     Hermanni Hyytiälä <address@hidden>      03/03/27 09:20:37

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

Log message:
        Update

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

Patches:
Index: gzz/Documentation/misc/hemppah-progradu/masterthesis.tex
diff -u gzz/Documentation/misc/hemppah-progradu/masterthesis.tex:1.199 
gzz/Documentation/misc/hemppah-progradu/masterthesis.tex:1.200
--- gzz/Documentation/misc/hemppah-progradu/masterthesis.tex:1.199      Thu Mar 
27 05:13:04 2003
+++ gzz/Documentation/misc/hemppah-progradu/masterthesis.tex    Thu Mar 27 
09:20:37 2003
@@ -1668,12 +1668,12 @@
 from recent publications. For general discussion about Fenfire in Peer-to-Peer 
environment, 
 see \cite{lukka02freenetguids}, and for detailed Storm design, see 
\cite{fallenstein03storm}.
 
-Storm (for \emph{STORage Module}) stores all data as data \emph{blocks}, which
+Storm (for \emph{STORage Module}) stores all data as \emph{blocks}, which
 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
+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 
+considered as a collision free hash function. Therefore, it is very unlikely 
that two different Storm blocks 
 would have same identifier.} \cite{fips-sha-1} is used
 for creating unstructured and semantic-free, globally unique identifiers for 
blocks. Because of SHA-1
 content hash, all identifiers are directly the data verifiers as well. The 
uniqueness of blocks creates 
@@ -1688,7 +1688,7 @@
 More information about diffs can be found from \cite{fallenstein03storm}. 
  
 \emph{Pointer} \cite{benja02urn5, fallenstein03storm} is a semantic-free 
updatable reference to 
-Storm data block. Pointer is a unique reference to the data and it is usually 
+Storm block. Pointer is a unique reference to the data and it is usually 
 represented as a random string. Storm pointers are rather a \emph{concept} of 
data (e.g., ''The front page of the most recent 
 version of New York Times newspaper'') whereas blocks \emph{contain} the data 
 (''New York Times newspaper, 10.10.2002, version 1.0'').
@@ -1760,8 +1760,8 @@
 \emph{global} data repository\footnote{Global repository is not a requirement. 
Locally constructed xanalogical
 documents are feasible and they can be assembled without global data 
repository.}. System implementing the xanalogical storage model \emph{must}
 support global scale data lookups, i.e., if a data item exists in the system 
it can be located and fetched. 
-Specifically, our task is to locate and fetch (i.e., obtain) all Storm 
blocks\footnote{We call these blocks as \emph{scroll} blocks.}, 
-associated to a specific ''virtual file'' from the Peer-to-Peer network. Also, 
in addition to the
+Specifically, our task is to locate and fetch (i.e., obtain) all Storm blocks, 
+associated to a specific ''virtual file'' from the Peer-to-Peer 
network\footnote{We call''associated'' blocks as \emph{scroll} blocks.}. Also, 
in addition to the
 \emph{direct} block obtaining using globally unique identifier of Storm block, 
 we also must support the \emph{indirect} obtaining of Storm block using the 
pointer mechanism. 
 Second, we want that users' operations in Fenfire