[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/10 14:15:41

Modified files:
        pointers       : article.rst 

Log message:
        Reviewing with Benja

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

Patches:
Index: manuscripts/pointers/article.rst
diff -u manuscripts/pointers/article.rst:1.228 
manuscripts/pointers/article.rst:1.229
--- manuscripts/pointers/article.rst:1.228      Mon Nov 10 14:04:18 2003
+++ manuscripts/pointers/article.rst    Mon Nov 10 14:15:40 2003
@@ -178,7 +178,7 @@
        The ability to 
        download versions and use them off-line without 
        a change in the user interface or functionality
-       and to use a neighbouring computer's cache
+       and the ability to use a neighbouring computer's cache
        if the LAN is disconnected from the Internet.
        Clicking on a link should "just work" when off-line,
        as long as the target is available locally.
@@ -202,8 +202,8 @@
 web pages cannot be updated:
 a new version of a web page would have a different hash,
 and thus a different URI. [#update]_
-Other approaches to versioning 
-that rely on keeping information about the current version
+Other approaches to versioning, which
+rely on keeping information about the current version
 in one place on one P2P network will not allow the heterogeneity of different
 systems to flourish.
 
@@ -217,7 +217,7 @@
 along with the corresponding version of a document.
 To find the current version, we search
 the whole P2P network for pointer records
-related to a document.
+about a document.
 
 An additional contribution is the Storm data model,
 an API formalizing the notion of searching for data
@@ -245,10 +245,9 @@
 would have the benefits of semantic-free referencing--
 URIs don't have to change because of trademark conflicts
 as in DNS, for example-- but go beyond the proposal
-by Balakrishnan et.al. [balakrishnan03semanticfree]_
+[balakrishnan03semanticfree]_
 to replace DNS but keep the centralized architecture of
-one Web server (or a single set of servers) maintained
-by the publisher of a document.
+Web servers.
 
 The remainder of this paper is structured as follows.
 In Section 2, we discuss how existing P2P systems handle updating.