[Gzz-commits] manuscripts/pointers article.rst review-jvk.txt

[Tuomas J. Lukka]

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

Modified files:
        pointers       : article.rst 
Added files:
        pointers       : review-jvk.txt 

Log message:
        Jvk's comments

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/pointers/review-jvk.txt?rev=1.1
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/pointers/article.rst.diff?tr1=1.175&tr2=1.176&r1=text&r2=text

Patches:
Index: manuscripts/pointers/article.rst
diff -u manuscripts/pointers/article.rst:1.175 
manuscripts/pointers/article.rst:1.176
--- manuscripts/pointers/article.rst:1.175      Sat Nov  8 10:43:21 2003
+++ manuscripts/pointers/article.rst    Sun Nov  9 13:36:46 2003
@@ -31,6 +31,8 @@
 Abstract
 ========
 
+.. XXX End half of paragraph untrue: oceanstore
+
 The Web could benefit greatly from the bandwith savings,
 increased availability, and reduced server costs offered
 by filesharing systems.
@@ -46,6 +48,9 @@
 ..  However, current P2P system do not provide adequate versioning
     because 
 
+.. XXX (jvk's comment) the next sentence should start with 
+   "To do X, we propose", 
+
 We propose *pointer records*, 
 signed files containing a document's id, 
 its current version's hash, and a timestamp.
@@ -95,6 +100,9 @@
 .. Introduce location-independent Web idea (citing
    benefits from hash-based addressing)---
 
+Filesharing systems [gnutellaurl-andalso-edonkey2kurl]_ 
+allow users to let others download
+files on their hard disks.
 If the Web worked like a filesharing system, there would be
 no central point of failure for a web page; a page could be downloaded
 from any host with a copy. This would save bandwidth
@@ -112,6 +120,9 @@
    infeasible to update all pages linking to it, and thus
    all pages linking to *them*, and thus...
 
+.. 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 the benefits of a filesharing system: 
@@ -317,9 +328,11 @@
 the entity that has change control over the document.
 This can be the owner's public key, or information about the CA
 from which the owner's current public key can be obtained.
-The charter can also include a semantic-free random
-bitstring, to distinguish the pointer from all other documents
-owned by the same entity.
+The charter also includes information
+to distinguish the pointer from all other documents
+owned by the same entity, for example
+a semantic-free random
+bitstring, 
 
 To associate pointers with versions, our system uses *pointer records*:
 small files that, similar to OceanStore's heartbeats,
@@ -459,7 +472,7 @@
 The pointer functionality is trivial to implement
 *on top of* this basic model. A pointer record
 is simply a special kind of block. A pointer record index
-is used to publish mappings from pointer ids
+is used to publish the mapping from pointer ids
 to the block ids of pointer records. [#]_
 
 .. [#] It may be useful, though, to implement an optimization
@@ -677,8 +690,8 @@
 ================
 
 We would like to thank Toni Alatalo, |Hermanni|, 
-Antti-Juhani Kaijanaho (who also proposed the name Storm)
-and Matti Katila for comments and discussions.
+Antti-Juhani Kaijanaho (who also proposed the name Storm),
+Matti Katila, and Janne Kujala for comments and discussions.
 
 .. XXX who else