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 researc...


From: Hermanni Hyytiälä
Subject: [Gzz-commits] gzz/Documentation/misc/hemppah-progradu researc...
Date: Tue, 21 Jan 2003 07:44:01 -0500

CVSROOT:        /cvsroot/gzz
Module name:    gzz
Changes by:     Hermanni Hyytiälä <address@hidden>      03/01/21 07:43:36

Modified files:
        Documentation/misc/hemppah-progradu: research_problems 

Log message:
        Almost everything required for thesis. Next, improvements, include more 
refs  and small additions. Then, write a story

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/gzz/Documentation/misc/hemppah-progradu/research_problems.diff?tr1=1.26&tr2=1.27&r1=text&r2=text

Patches:
Index: gzz/Documentation/misc/hemppah-progradu/research_problems
diff -u gzz/Documentation/misc/hemppah-progradu/research_problems:1.26 
gzz/Documentation/misc/hemppah-progradu/research_problems:1.27
--- gzz/Documentation/misc/hemppah-progradu/research_problems:1.26      Tue Jan 
21 07:07:40 2003
+++ gzz/Documentation/misc/hemppah-progradu/research_problems   Tue Jan 21 
07:43:36 2003
@@ -768,7 +768,7 @@
 Tomorrow's computer environment will involve vast, constant media downloads.  
ZigZag structure offers a scalable, rational system of registration and storage 
which can handle this very cleanly.
 3.  A new form of SPATIAL PROGRAMMING, table-driven in zzspace, may simplify 
programming and computer environments in general.
 
-5. Problmes related to P2P
+5. Problems related to P2P
 
 5.1. Misc
 -Could we use SDSI/SPKI in our system (it's hierarchical), like in ConChord 
\cite{ajmani02conchord}
@@ -777,7 +777,7 @@
 -in our model: trust = trust no one
 -give a brief explanation of current techiques in accountability and trust
 
-Tuomas' example scenario (in finnish):
+Tuomas' example scenario #1(in finnish):
 
 jos joku sanoo, ett? urn-5 foo on blokeissa X
 ja j?tt?? blokit Y pois
@@ -789,7 +789,8 @@
 floodaamalla indeksi
 mutta sitten poistamalla ne serverit
 
-What will happen if, jyu's network connection is broken ? Inside jyu, how do 
we will self-organise ?
+Tuomas' example scenario #2:
+'What will happen if, jyu's network connection is broken ? Inside jyu network, 
how do we/system will self-organise ?'
 
 Half-life phenomenon \cite{libennowell01observations}
 Current decentralized, but structured \cite{chord, can, pastry, Tapestry etc.) 
ignores the fact 
@@ -813,7 +814,30 @@
 underlying network properties
 
 Security issues related to p2p, create by Ross Lee Graham:
-http://www.ida.liu.se/~rosgr/p2psecurity.html 
+http://www.ida.liu.se/~rosgr/p2psecurity.html
+
+Principles on scalable search in decentralized, and unstructured networks 
\cite{lv02searchreplication}:
+1) system must support adaptive termination 
+2) message duplication should be minimized
+3) each additional step during search should not significantly increase the 
number of nodes visited
+
+Main problems in different approaches (own conclusions, based on research 
efforts):
+1) Decentralized, but structured
+-make routing/system more flexible againts adversial attacks
+       -e.g. -there is a single point of routing failure in these approaches 
(h hops, little amount f of system are adversial)
+-make searching/query model more flexible (keyword searching)
+       -use keywords/range searches instead of exact keys
+       proposal for range searches: Scalable, Efficient Range Queries for Grid 
Information Services \cite{andrzejak02rangequeries}
+
+2) Decentralized, but unstructured
+-make routing more scalable: reach more nodes, create less traffic
+-remember mention: when people talk about Gnutella's scalability issues
+they jumble apples and oranges: *Gnutella* itself is scalable, but query model 
+is not scalable, since searching creates a lot of traffic!
+
+3) Centralized
+-no recent research efforts/no interests
+-not suitable for real p2p, as Napster case showed
 
 5.2. Open Problems in p2p data-sharing \cite{daswani03openproblems}
 




reply via email to

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