gzz-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gzz-commits] manuscripts/pointers article.rst


From: Benja Fallenstein
Subject: [Gzz-commits] manuscripts/pointers article.rst
Date: Thu, 06 Nov 2003 08:39:08 -0500

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Branch:         
Changes by:     Benja Fallenstein <address@hidden>      03/11/06 08:39:08

Modified files:
        pointers       : article.rst 

Log message:
        main points

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

Patches:
Index: manuscripts/pointers/article.rst
diff -u manuscripts/pointers/article.rst:1.150 
manuscripts/pointers/article.rst:1.151
--- manuscripts/pointers/article.rst:1.150      Thu Nov  6 08:31:14 2003
+++ manuscripts/pointers/article.rst    Thu Nov  6 08:39:07 2003
@@ -13,6 +13,22 @@
 Abstract
 ========
 
+- The Web should keep previous versions as long as someone
+  is interested, even if the original publisher has lost interest
+- File sharing systems kind of do that
+- But you can't update files in them
+- P2P systems that do support updating don't support
+  this notion of permanence
+- We present a simple model that *does* do it
+- We present an even simpler model that it could be
+  implemented upon; the simpler model maps directly
+  to many current p2p systems
+- It can thus use different P2P networks as backends,
+  and could thus become a agreed-upon way to do
+  versioning (we believe that the current systems,
+  which require state to be kept in *one* of the networks
+  really can not)
+
 The Web could benefit greatly from the bandwith savings,
 increased availability, and reduced server costs offered
 by filesharing systems.




reply via email to

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