[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/13 08:27:25

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

Log message:
        Misc updates everywhere

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

Patches:
Index: gzz/Documentation/misc/hemppah-progradu/masterthesis.tex
diff -u gzz/Documentation/misc/hemppah-progradu/masterthesis.tex:1.138 
gzz/Documentation/misc/hemppah-progradu/masterthesis.tex:1.139
--- gzz/Documentation/misc/hemppah-progradu/masterthesis.tex:1.138      Thu Mar 
13 08:18:54 2003
+++ gzz/Documentation/misc/hemppah-progradu/masterthesis.tex    Thu Mar 13 
08:27:21 2003
@@ -86,12 +86,8 @@
 and connecting to each other directly. Additionally, the distributed and ad 
hoc nature of 
 Peer-to-Peer improves scalability and avoids single points of failure.
 
-There are many definitions of Peer-to-Peer networks. The Intel Peer-to-Peer 
-Working Group defines it as ''the sharing of computer resources and services 
-by direct exchange between systems'' \cite{p2pworkinggroup}. 
-Dave Winer \cite{winer00whatisp2p} describes Peer-to-Peer systems as
-''The user's machine is a client and a server''. 
-Schollmeier \cite{schollmeier01p2pdefinition} characterizes a Peer-to-Peer 
system as a system of 
+There are many definitions of Peer-to-Peer networks. Schollmeier 
\cite{schollmeier01p2pdefinition} 
+describes a Peer-to-Peer system as a system of 
 distributed entities that share their own services. Thus, Peer-to-Peer systems 
can be characterized as distributed 
 systems in which all communication is symmetric and all participants entities 
have similar 
 capabilities and responsibilities. Each entity, i.e., \emph{peer}, may 
contribute services 
@@ -104,7 +100,7 @@
 Peer-to-Peer systems and divide problems into three sub-categories: security 
problems, 
 performance problems and miscellaneous problems.  
 
-Next, we give an overview of Fenfire project. Fenfire project is an attempt to 
build hyperstructured,
+We give an overview of Fenfire project. Fenfire project is an attempt to build 
hyperstructured,
 seamlessly interoperating desktop environment. Additional features of Fenfire 
include innovative user 
 interfaces for viewing data and usage of Peer-to-Peer networking for network 
transparency. In Fenfire, 
 all data is stored in the same format, i.e., data blocks.  All blocks have 
globally unique 
@@ -797,7 +793,7 @@
 \parbox{37pt}{$O(1)$} &
 \parbox{37pt}{$O(1)$} &
 \parbox{37pt}{$O(n)$} &
-\parbox{85pt}{Can be 1-10000 connections (aka social connections, connections 
are permanent)} &
+\parbox{85pt}{Can be 1-10000 connections (as known as ''social'' connections, 
connections are permanent)} &
 \parbox{85pt}{Number of connections number depends on peer's memory/network 
capabilities}
 \\ \hline
 
@@ -1191,7 +1187,7 @@
 structured system, peers join and leave the system constantly without any 
restrictions. On the
 other hand, however, peers in tightly structured system have less freedom, 
i.e. overlay chooses peer's
 neighbors on behalf of peer itself and maps data items randomly throughout the 
overlay network. However,
-Peer-to-Peer system is \emph{never} in ''ideal'' state as it is continuouslys 
evolving system.
+Peer-to-Peer system is \emph{never} in ''ideal'' state as it is continiously 
evolving system.
 
 Current research has been focused on system management of tightly structured 
systems, and all presented
 algorithms of tightly structured approach have been analyzed under static 
simulation environments. Furthermore, proposed