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: Fri, 17 Jan 2003 08:05:15 -0500

CVSROOT:        /cvsroot/gzz
Module name:    gzz
Changes by:     Hermanni Hyytiälä <address@hidden>      03/01/17 08:05:15

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

Log message:
        bitTorrent

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

Patches:
Index: gzz/Documentation/misc/hemppah-progradu/research_problems
diff -u gzz/Documentation/misc/hemppah-progradu/research_problems:1.17 
gzz/Documentation/misc/hemppah-progradu/research_problems:1.18
--- gzz/Documentation/misc/hemppah-progradu/research_problems:1.17      Fri Jan 
17 05:05:53 2003
+++ gzz/Documentation/misc/hemppah-progradu/research_problems   Fri Jan 17 
08:05:14 2003
@@ -111,9 +111,28 @@
 -not network/geographical locality
 
 See summary table for performance details
-  
 
-1.7. Summary
+
+1.7. BitTorrent
+Notice: pros and cons are not presented here
+-BitTorrent is not a lookup system-- it's a tool for *distributing* data
+-MIT License, written in Python
+-resembles Overnet's/ed2k's MFTP
+-supports resumed downloads
+-supports upload-download ratios (if this is a built in feature, this might be 
a problem for us (if used as out-of-box))
+-however, upload-download ratios reduces DoS attacks: one cannot publish a 
large amount hokum data in the network if ratios are used
+-reduces query hotspots (DHTs), however routing hotspots remain
+-when more than one person is downloading from a server/node/computer, 
BitTorrent sends blocks of the files to downloaders
+-this reserves the server's/node's/computer's bandwidth
+-supports simultaenous downloads
+-since each new downloader introduces a new upload capacity, eventually the 
upload overhead for the original server/node/computer bandwidth is reasonable 
small
+-uses SHA-1 for checking data integrity (suits for us very well!)
+-we don't have to create 'mini-blocks' for Gzz p2p, since bitTorrent itself 
partitions data into several blocks for us
+-my initial suggestion for our p2p data obtaining scheme: use Kademlia for 
data lookup and bitTorrent/MFTP-like tool for downloading the data
+
+See http://bitconjurer.org/BitTorrent/ for details.  
+
+1.8. Summary
 
 This summary table is far from complete (and from total truth)
 




reply via email to

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