[Gzz-commits] manuscripts ./gzigzag.bib pointers/article.rst

[Benja Fallenstein]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Branch:         
Changes by:     Benja Fallenstein <address@hidden>      03/11/02 13:56:38

Modified files:
        .              : gzigzag.bib 
        pointers       : article.rst 

Log message:
        put in refs

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/gzigzag.bib.diff?tr1=1.146&tr2=1.147&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/pointers/article.rst.diff?tr1=1.76&tr2=1.77&r1=text&r2=text

Patches:
Index: manuscripts/gzigzag.bib
diff -u manuscripts/gzigzag.bib:1.146 manuscripts/gzigzag.bib:1.147
--- manuscripts/gzigzag.bib:1.146       Thu Oct 30 05:42:36 2003
+++ manuscripts/gzigzag.bib     Sun Nov  2 13:56:37 2003
@@ -1740,6 +1740,12 @@
   pages =        {40--49}
 }
 
address@hidden,
+  author =       {The {F}reenet {P}roject},
+  title =        {Frequently {A}sked {Q}uestions},
+  howpublished = {\url{http://www.freenetproject.org/index.php?page=faq}}
+}
+
 @Misc{what-is-p2p,
   author =       {Clay Shirky},
   title =        {What Is P2P ... And What Isn't},
Index: manuscripts/pointers/article.rst
diff -u manuscripts/pointers/article.rst:1.76 
manuscripts/pointers/article.rst:1.77
--- manuscripts/pointers/article.rst:1.76       Sun Nov  2 13:46:50 2003
+++ manuscripts/pointers/article.rst    Sun Nov  2 13:56:38 2003
@@ -59,8 +59,8 @@
 and thus a different URI.
 
 There are a few (non-file-sharing) P2P systems 
-that do offer an update mechanism. *CFS* [XXXref] 
-is a file system based on Chord [XXXref], storing
+that do offer an update mechanism. *CFS* [dabek01widearea]_
+is a file system based on Chord [stoica01chord]_, storing
 data in a distributed hashtable (DHT). CFS identifies
 different users' trees by the users' cryptographic keys;
 it stores in its DHT mappings from these keys to the
@@ -69,7 +69,7 @@
 is signed with the appropriate key, and contains a timestamp
 newer than that of the current version.
 
-In *Oceanstore* [XXXref], every document has a
+In *Oceanstore* [kubiatowicz00oceanstore]_, every document has a
 *primary replica*, a small set of servers that
 maintain the current version of the document.
 To make the connection between document and version,
@@ -86,13 +86,13 @@
 allowing previous versions of documents to be accessed
 (by using their old heartbeats).
 
-*Freenet* [XXXref] was originally planned to have an
+*Freenet* [freenet-ieee]_ was originally planned to have an
 update mechanism where the network would remember
 the current version of a document, and update this information
 when receiving a message signed by the appropriate key,
-rather like in Oceanstore [XXXref]. However, in practice,
+rather like in Oceanstore. However, in practice,
 Freenet has a rather peculiar combination 
-of two workarounds [XXXref Freenet FAQ]:
+of two workarounds [freenetfaq]_:
 
 In date-based updating, the URI for the current version
 is formed by concatenating a document's id with the current date;
@@ -109,7 +109,7 @@
 Finally, a simplistic approach to P2P versioning
 is to have a centralized server keep track of the current version
 of a document, such as in the *Content-Addressable Web* 
-proposal [XXXref -> google it], in which clients download 
+proposal [content-addressable-web]_, in which clients download 
 a file's hash through HTTP (using an HTTP URI),
 then download the file through, e.g., a file-sharing network.
 This provides some of the efficiency advantages of a P2P Web.
@@ -195,7 +195,7 @@
 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. [XXXref], which would only
+by Balakrishnan et.al. [balakrishnan03semanticfree]_, which would only
 replace DNS, but keep the centralized architecture of
 one Web server (or a single set of servers) maintained
 by the publisher of a document.