[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/25 10:48:10

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

Log message:
        Clarify better

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

Patches:
Index: gzz/Documentation/misc/hemppah-progradu/masterthesis.tex
diff -u gzz/Documentation/misc/hemppah-progradu/masterthesis.tex:1.189 
gzz/Documentation/misc/hemppah-progradu/masterthesis.tex:1.190
--- gzz/Documentation/misc/hemppah-progradu/masterthesis.tex:1.189      Tue Mar 
25 09:57:30 2003
+++ gzz/Documentation/misc/hemppah-progradu/masterthesis.tex    Tue Mar 25 
10:48:10 2003
@@ -1799,13 +1799,11 @@
 structured overlays; the tightly structured overlay supports global data 
lookups
 in the overlay, whereas the data lookup model of the loosely structured 
approach
 is limited to a certain area of the overlay\footnote{The area depends on where 
the query
-originator is located in the overlay.}.
+originator is located in the overlay.}. To summarize, the tightly structured 
approach
+is more efficient and scalable than the loosely structured approach.
 
-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., Storm provides globally unique identifiers which can be used in 
the
-tightly structured overlay.
+Since both Storm and tightly structured overlays use globally unique 
identifiers for each,
+it is feasible to use tightly structured overlays for \emph{locating} Storm 
blocks efficiently.
 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