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: Tuomas J. Lukka
Subject: [Gzz-commits] manuscripts/pointers article.rst
Date: Mon, 10 Nov 2003 03:19:41 -0500

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Branch:         
Changes by:     Tuomas J. Lukka <address@hidden>        03/11/10 03:19:40

Modified files:
        pointers       : article.rst 

Log message:
        Theses: what should a P2P web offer

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

Patches:
Index: manuscripts/pointers/article.rst
diff -u manuscripts/pointers/article.rst:1.180 
manuscripts/pointers/article.rst:1.181
--- manuscripts/pointers/article.rst:1.180      Mon Nov 10 02:56:45 2003
+++ manuscripts/pointers/article.rst    Mon Nov 10 03:19:40 2003
@@ -128,18 +128,28 @@
 .. XXX Mention "Name-based not possible as a suitable system
    for names doesn't exist?"
 
-There are some non-filesharing P2P systems 
-that do offer an update mechanism. However, none of these
-provides all the benefits of a filesharing system: 
+We hold that to succeed, a P2P Web would need to provide
+the following features for users: 
 
-- Being able to download version(s) and use off-line
-- Being able to use neighbour's computer's cache
-  if your LAN is disconnected
-- Being able to keep version online for as long as you want
-- Being able to use different networks: a) withstand
-  exploit of single network; b) one size doesn't fit all
-  (e.g. anonymity, efficiency); c) more people can use this
-  (network effect)
+Off-line capability 
+       The ability to 
+       download version(s) and use them off-line without 
+       a change in the user interface or functionality, 
+       and to use a neighbouring computer's cache
+       if the LAN is disconnected from the internet 
+Heterogeneity
+       The possibility to
+       use different P2P networks interchangeably 
+       to
+       a) withstand
+       exploits of single network; b) one size doesn't fit all
+       (e.g. anonymity, efficiency); c) more people can use this
+       (network effect)
+Distributed archivability
+       The ability to
+       keep a version originally published by 
+       someone else online, *accessible to others*,
+       for any period of time 
 
 .. To keep a version 
    of a page online, it does not suffice for one user
@@ -157,6 +167,10 @@
     and stops publishing a page, it disappears, even if
     someone else has kept a copy.
 
+There are some non-filesharing P2P systems 
+that do offer an update mechanism. However, none of these
+provides all the above benefits of a filesharing system: 
+
 ...
 
 Permanence is an important concern, as seen by the following example.
@@ -245,7 +259,7 @@
 ============
 
 In this section, we shall briefly discuss the existing approaches
-to document updates in P2P systems.
+to versioning in P2P systems.
 
 A trivial approach to P2P versioning
 is to have a centralized server keep track of the current version




reply via email to

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