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 01:41:47 -0500

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

Modified files:
        pointers       : article.rst 

Log message:
        s/Web page/web page/

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

Patches:
Index: manuscripts/pointers/article.rst
diff -u manuscripts/pointers/article.rst:1.136 
manuscripts/pointers/article.rst:1.137
--- manuscripts/pointers/article.rst:1.136      Thu Nov  6 01:40:05 2003
+++ manuscripts/pointers/article.rst    Thu Nov  6 01:41:47 2003
@@ -7,9 +7,8 @@
 
 .. XXX Abstract is too long ;)
 
-.. XXX Decide on spelling Web page / web page / webpage
-   OED says the second one; I'd prefer the third;
-   there are several instances of the first here...
+.. XXX Decide on spelling web page / webpage
+   OED says the first; Tuomas would prefer the second.
 
 Abstract
 ========
@@ -45,7 +44,7 @@
 
 
 ..  This loses a major benefit of filesharing:
-    To keep a version of a Web page available, 
+    To keep a version of a web page available, 
     it should suffice to keep a copy of it on your computer.
 
 ..  Instead of being handled specially by a P2P network,
@@ -73,15 +72,15 @@
    benefits from hash-based addressing)---
 
 If the Web worked like a filesharing system, there would be
-no central point of failure for a Web page; it could be downloaded
+no central point of failure for a web page; it could be downloaded
 from any host that has a copy. This would save bandwidth
 and increase availability. However, if the Web worked like
-a filesharing system, Web pages could not be updated.
+a filesharing system, web pages could not be updated.
 Some filesharing systems offer permanent URIs for files 
 (e.g., [freenet-ieee-andalso-edonkey2kurl]_),
 based on the files' cryptographic hashes,
 which could be used for linking; but
-a new version of a Web page would have a different hash,
+a new version of a web page would have a different hash,
 and thus a different URI. [#update]_
 
 .. [#update] When updating a page, it would be clearly
@@ -449,7 +448,7 @@
 .. XXX heterogeneous *how*?
 
 Using pointer records, we can provide the functionality
-of static Web pages. While dynamic Web pages generated
+of static web pages. While dynamic web pages generated
 through server-side scripting and database connections
 are certainly important, this still makes up for 
 a significant portion of today's Web.
@@ -552,7 +551,7 @@
 created by pointer records. 
 Through a simple reverse index, it was also easy to implement
 a "backlinks" functionality, which tells the user which
-pages link *to* a given Web page.
+pages link *to* a given web page.
 When run on the local machine,
 documents owned by the machine's owner can also be
 edited through simple WebDAV clients.




reply via email to

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