[Gzz-commits] manuscripts/pointers article.rst

[Tuomas J. Lukka]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Branch:         
Changes by:     Tuomas J. Lukka <address@hidden>        03/11/04 04:36:30

Modified files:
        pointers       : article.rst 

Log message:
        Organize and cut down abstract size

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/pointers/article.rst.diff?tr1=1.118&tr2=1.119&r1=text&r2=text

Patches:
Index: manuscripts/pointers/article.rst
diff -u manuscripts/pointers/article.rst:1.118 
manuscripts/pointers/article.rst:1.119
--- manuscripts/pointers/article.rst:1.118      Tue Nov  4 04:27:43 2003
+++ manuscripts/pointers/article.rst    Tue Nov  4 04:36:30 2003
@@ -9,21 +9,17 @@
 Abstract
 ========
 
-Filesharing systems save bandwidth and increase availability
-because there is no single point of failure for a file.
-This would be desirable on the Web.
+The Web could benefit greatly from the bandwith savings,
+increased availability, and reduced server costs offered
+by filesharing systems by eliminating single points of failure.
 However, most current P2P systems have no facility 
 for updating documents, and those that do 
-require keeping the current version as state in the network.
-This loses a major benefit of filesharing:
-To keep a version of a Web page available, 
-it should suffice to keep a copy of it on your computer.
+require keeping track of the current version as extra state in the network.
+
+..  This loses a major benefit of filesharing:
+    To keep a version of a Web page available, 
+    it should suffice to keep a copy of it on your computer.
 
-In this paper, we present a simple versioning mechanism usable
-for a P2P Web as well as for filesharing,
-and P2P-based software distribution and upgrading,
-and serve as a common versioning model integrating
-separate P2P networks.
 Extending OceanStore's "heartbeats," we propose *pointer records*, 
 signed files containing a document's id, 
 its current version's hash, and a timestamp.
@@ -31,8 +27,14 @@
 through the same mechanism we use to find files by hash
 (for example, a DHT). 
 To find the newest version, we look for the most recent timestamp.
-This way, versions of a document 
+This way, past versions of a document 
 stay available as long as anybody keeps a copy.
+Pointer records 
+can serve as a common versioning model integrating
+separate P2P networks, 
+and can be used
+for a P2P Web as well as for filesharing,
+and P2P-based software distribution and upgrading,