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: Mon, 27 Oct 2003 06:29:11 -0500

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Branch:         
Changes by:     Benja Fallenstein <address@hidden>      03/10/27 06:29:11

Modified files:
        pointers       : article.rst 

Log message:
        intro bullet points into comments; in contribs, change nonlinear 
versioning to diffing

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

Patches:
Index: manuscripts/pointers/article.rst
diff -u manuscripts/pointers/article.rst:1.7 
manuscripts/pointers/article.rst:1.8
--- manuscripts/pointers/article.rst:1.7        Mon Oct 27 06:25:21 2003
+++ manuscripts/pointers/article.rst    Mon Oct 27 06:29:10 2003
@@ -12,46 +12,50 @@
 Introduction
 ============
 
-- Introduce location-independent Web idea (citing
-  benefits from hash-based addressing)
+.. Introduce location-independent Web idea (citing
+   benefits from hash-based addressing)---
 
-  - Standing on the shoulders of giants: Example of Web links rotting away
-  - History of location-dependence: `TBL ref`_ (like in HT'03 paper)
-  - Location-independent, semantic-free, *self-verifying* 
-    identifiers (ref SFR paper (Balakrishnan et.al. IPTPS'03),
-    ref Walfish paper); example: hash-based (ref 
-    ``hash`` URN namespace Internet-Draft; ref Freenet & others)
-  - Proposal: A location-independent Web (closest thing is Freenet (ref))
-  - Benefits of hash-based addressing
-
-    - Pages easily movable between servers
-    - Data accessible as long as anyone keeps a copy
-    - Load balancing (download from everyone who has a copy)
-    - Can use one addressing scheme with different protocols,
-      searching different networks for the content behind a hash
-
-  - SFR (semantic-free referencing) not all that close, 
-    though semantic-free idea shared (SFR takes along 
-    many problems of the Web)
-  - Other projects exploit some of the advantages of hash-based
-    (storage systems: CFS, PAST; web caching: Squirrel),
-    but don't address the Web.
-  - Possibility of desktop integration in ways that the location-dependent
-    Web cannot archieve, through the unique combination of
-    network transparency and location independence (ref ourselves).
-
-- However, there's a problem with this: versioning
-
-  - Basic problem: Hash-based addressing allows no updates
-
-- Contributions; structure of this paper
-
-  - Main contrib: Pointer records for implementing updating
-  - Other contribs:
-
-    - The idea of a location-independent Web including
-      location-independent version management
-    - Non-linear versioning through obsoletion
+.. Standing on the shoulders of giants: Example of Web links rotting away
+
+.. History of location-dependence: `TBL ref`_ (like in HT'03 paper)
+
+.. Location-independent, semantic-free, *self-verifying* 
+   identifiers (ref SFR paper (Balakrishnan et.al. IPTPS'03),
+   ref Walfish paper); example: hash-based (ref 
+   ``hash`` URN namespace Internet-Draft; ref Freenet & others)
+
+.. Proposal: A location-independent Web (closest thing is Freenet (ref))
+
+.. Benefits of hash-based addressing:
+   - Pages easily movable between servers
+   - Data accessible as long as anyone keeps a copy
+   - Load balancing (download from everyone who has a copy)
+   - Can use one addressing scheme with different protocols,
+     searching different networks for the content behind a hash
+
+.. SFR (semantic-free referencing) not all that close, 
+   though semantic-free idea shared (SFR takes along 
+   many problems of the Web)
+
+.. Other projects exploit some of the advantages of hash-based
+   (storage systems: CFS, PAST; web caching: Squirrel),
+   but don't address the Web.
+
+.. Possibility of desktop integration in ways that the location-dependent
+   Web cannot archieve, through the unique combination of
+   network transparency and location independence (ref ourselves).
+
+.. However, there's a problem with this: versioning -----
+   Basic problem: Hash-based addressing allows no updates
+
+.. Contributions; structure of this paper ----
+
+.. Main contrib: Pointer records for implementing updating
+
+.. Other contribs:
+   - The idea of a location-independent Web including
+     location-independent version management
+   - Diffs
 
 
 Related work




reply via email to

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