[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/24 11:16:49

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

Log message:
        fixes

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

Patches:
Index: gzz/Documentation/misc/hemppah-progradu/masterthesis.tex
diff -u gzz/Documentation/misc/hemppah-progradu/masterthesis.tex:1.179 
gzz/Documentation/misc/hemppah-progradu/masterthesis.tex:1.180
--- gzz/Documentation/misc/hemppah-progradu/masterthesis.tex:1.179      Mon Mar 
24 11:08:33 2003
+++ gzz/Documentation/misc/hemppah-progradu/masterthesis.tex    Mon Mar 24 
11:16:49 2003
@@ -1663,11 +1663,11 @@
 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\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.} cryptographic content hash function 
\cite{fips-sha-1} is used
+are immutable byte sequences. 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
-content hash, all identifiers are directly the data verifiers as well. The 
uniquess of data creates 
+content hash, all identifiers are directly the data verifiers as well. The 
uniquess of blocks creates 
 a basis for implementing xanalogical storage model in the Fenfire system. 
Storm blocks have much in common with regular files as they
 both contain the data. The main difference is that Storm blocks are 
\emph{immutable} since any 
 change to the byte sequence would change block's hash value (globally unique 
identifier).  
@@ -1678,26 +1678,25 @@
 paper, however, we discuss only pointers as they are part of the thesis' 
research problems. 
 More information about diffs can be found from \cite{fallenstein03storm}. 
  
-Pointer \cite{benja02urn5, fallenstein03storm} is a semantic-free updatable 
reference to 
-Storm data block, i.e., a Storm scroll block. Pointer is unique reference to 
the data and it is usually 
-represented as a random string. Storm pointers blocks are rather a 
\emph{concept} of data (e.g., ''The first page of the most recent 
-version of New York Times newspaper'') whereas Storm scroll blocks 
\emph{contain} the data 
+\emph{Pointer} \cite{benja02urn5, fallenstein03storm} is a semantic-free 
updatable reference to 
+Storm data block, i.e., Storm scroll block. Pointer is 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 first page of the most recent 
+version of New York Times newspaper'') whereas scroll blocks \emph{contain} 
the data 
 (''New York Times newspaper, 10.10.2002, version 1.0'').
 Figure \ref{fig:storm_model} illustrates simplified Storm storage model with 
pointers. 
 
 Each pointer is associated with a collection of \emph{pointer blocks}. 
-Pointers can be created by a user, before the creation of any pointer blocks. 
Pointer blocks 
+Pointers can be created by a user, before the creation of scroll blocks. 
Pointer blocks 
 are created automatically by Storm when a scroll block is associated with a 
pointer 
 (e.g., by a user when creating a concept of ''The first page of the most 
recent 
 version of New York Times newspaper''). Pointer block has always a single 
target (i.e., a scroll block) 
 for the pointer, saying that pointer $P$ targets block $B$. In addition to 
this, pointer block 
-may contain a list of zero or more obsoleted pointer blocks, i.e., when a new 
version of pointer 
+may contain a list of zero or more obsoleted pointer blocks: when a new 
version of pointer 
 block is created, it supersedes one older version which has been created in 
the past using the Storm indexing
-mechanisms. For details, see \cite{fallenstein03storm}. The most current 
pointer 
-block will ''obsolete'' the pointer block targeting the superseded version. 
Next 
+mechanisms. For details, see \cite{fallenstein03storm}. Next 
 time, when the pointer is used for referring to a specific scroll block, only 
 the most recent pointer's block target is loaded. However, the pointer blocks 
pointing
-to the previous versions remains accessible, if needed. In figure 
\ref{fig:storm_pointercreation}, 
+to the previous versions of scroll blocks remains accessible, if needed. In 
figure \ref{fig:storm_pointercreation}, 
 we show the overall pointer creation process. 
 
 \begin{figure}