gzz-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gzz-commits] manuscripts/storm article.rst


From: Benja Fallenstein
Subject: [Gzz-commits] manuscripts/storm article.rst
Date: Wed, 05 Feb 2003 16:32:17 -0500

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Benja Fallenstein <address@hidden>      03/02/05 16:32:17

Modified files:
        storm          : article.rst 

Log message:
        rm old crud

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

Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.87 manuscripts/storm/article.rst:1.88
--- manuscripts/storm/article.rst:1.87  Wed Feb  5 16:13:09 2003
+++ manuscripts/storm/article.rst       Wed Feb  5 16:32:17 2003
@@ -201,39 +201,12 @@
 available CFS servers. Freenet [ref] and PAST [ref, pastry ref] doesn't split 
 files into blocks, since they store data as whole files. All previously 
mentioned 
 systems lack of the immutable property which is used in Storm blocks.
-
    
 Related work: we need something about p2p hypermedia: 
 [ref Bouvin, Wiil ("Peer-to-Peer Hypertext")]
 
-[Note: The following are my notes for what should be written,
-not final text! --benja .. adding comments in the middle --antont]
-
 It's well recognized that references should not be by location [ref URN].
 
-(To explain ad hoc *data mobility*:
-Data moves like this and that. The server/location paradigm
-is not suited to this: To support hypermedia functionality correctly,
-we need to recognize two copies of the *same* document.
-Only then can we merge the fragmented worlds of desktop computing
-and online publishing into one.)
-
-Server centricity is what made the web scalable. Backlinks rejected
-for this reason [ref TBL -- XXX note: not true like this; the ref I had
-in mind is http://www.w3.org/DesignIssues/NameMyth.html, and
-it's not about back links]. However, recent innovations in P2P have made
-scalable location independent routing/hashtables possible.
-
-->
-Binding documents to servers has been necessary to make the Web scalable,
-as no central index of documents was needed.
-Berners-Lee [ref NameMyth] argues that identifying documents
-by unique, completely random identifiers may be desirable because
-there is never a need to change such an identifier because e.g. a server
-moves to a different organization, but that it is not possible to
-resolve 
-
-
 {If standards could be agreed on, web servers should be able to
 self-organize into a DHT implementing bidi links. There has been
 interest in p2p hypermedia [ref Bouvin, Wiil ("Peer-to-Peer Hypertext")]. 
@@ -293,25 +266,6 @@
 All of these use cases except train collaboration are in use *today*.
 To support hypermedia functionality well in these cases, we need to
 address the issues above.
-
-We present a design which addresses the issues we have raised.
-We are currently in prototype stage, which we describe...
-Along with the design, we illustrate how it supports various situations in
-the use cases. 
-
-->
-We present Storm (for *storage module*), a design which addresses the issues 
-we have described. 
-
-->
-We describe 
-the partially implemented Storm design, 
-a storage system designed to cope with two problems
-raised by moving documents: Dangling links [refs stating problem], 
-and keeping track of alternative versions [refs stating problem].
-
-
-
 
 
 3. Block storage




reply via email to

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