[Gzz-commits] manuscripts/storm SCRATCH article.rst

[Benja Fallenstein]

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

Modified files:
        storm          : SCRATCH article.rst 

Log message:
        move stuff to SCRATCH

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/storm/SCRATCH.diff?tr1=1.8&tr2=1.9&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/storm/article.rst.diff?tr1=1.97&tr2=1.98&r1=text&r2=text

Patches:
Index: manuscripts/storm/SCRATCH
diff -u manuscripts/storm/SCRATCH:1.8 manuscripts/storm/SCRATCH:1.9
--- manuscripts/storm/SCRATCH:1.8       Tue Jan 28 01:54:06 2003
+++ manuscripts/storm/SCRATCH   Wed Feb  5 20:05:56 2003
@@ -1,3 +1,48 @@
+In the future, dangling links may be an issue when using
+local resources [ref Thompton et al], for example in an ad-hoc
+network formed when two people with WLAN cards meet on the train.
+If one accesses the other's documents, link targets should be
+retrieved from the other's machine... XXX
+
+Also, after a document is published, local backlinks to it
+should be shown together along with public backlinks made by others.
+Efficiency can be improved if documents can
+be found on the local machine if they have been cached or downloaded,
+or from any peer that has a copy in its cache. 
+
+.. Examples for data mobility include today:
+
+   - sharing versions (email attachment, disk) -> versioning
+   - cvs-like central sync point(s) -> versioning
+   - off-line work (dialup, laptop/cellphone/pda) -> links
+   - publication -> links
+   - mirroring -> links
+   - downloading -> links, versioning if modified after download
+   - moving between own systems (desktop/laptop, work/home) ->
+     versioning, links
+   - web archive -> links, versioning (past versions)
+
+   Future visions:
+
+   - downloading from others' cache/permanent storage (load balancing) ->
+     links
+   - hosting on own computer. others mirror -> links
+   - ad-hoc sharing (train, cafe) -> links
+
+   Not really data mobility:
+
+   - comments and links on published document
+
+
+.. The design also allows for
+   automatic balancing of the load, which occurs in location-dependent
+   situations with popular items. [benja says: This is not related
+   to the central point as expressed in the title; therefore, I believe
+   it should be given as a benefit of the system somewhere later
+   in the paper (like many others) but not put here...]
+
+
+
 
 NOTE:
 a name is dereferencable (a block can be found) as long as
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.97 manuscripts/storm/article.rst:1.98
--- manuscripts/storm/article.rst:1.97  Wed Feb  5 20:03:33 2003
+++ manuscripts/storm/article.rst       Wed Feb  5 20:05:56 2003
@@ -71,52 +71,9 @@
 or when a link is sent by mail and the document is available
 from the local intranet.
 
-In the future, dangling links may be an issue when using
-local resources [ref Thompton et al], for example in an ad-hoc
-network formed when two people with WLAN cards meet on the train.
-If one accesses the other's documents, link targets should be
-retrieved from the other's machine... XXX
-
-Also, after a document is published, local backlinks to it
-should be shown together along with public backlinks made by others.
-Efficiency can be improved if documents can
-be found on the local machine if they have been cached or downloaded,
-or from any peer that has a copy in its cache. 
-
 Alternate versions are an issue when [syncing versions by mail/disk,
 central sync point, off-line work on shared repository,
 moving between own systems].
-
-
-.. Examples for data mobility include today:
-
-   - sharing versions (email attachment, disk) -> versioning
-   - cvs-like central sync point(s) -> versioning
-   - off-line work (dialup, laptop/cellphone/pda) -> links
-   - publication -> links
-   - mirroring -> links
-   - downloading -> links, versioning if modified after download
-   - moving between own systems (desktop/laptop, work/home) ->
-     versioning, links
-   - web archive -> links, versioning (past versions)
-
-   Future visions:
-
-   - downloading from others' cache/permanent storage (load balancing) ->
-     links
-   - hosting on own computer. others mirror -> links
-   - ad-hoc sharing (train, cafe) -> links
-
-   Not really data mobility:
-
-   - comments and links on published document
-
-.. The design also allows for
-   automatic balancing of the load, which occurs in location-dependent
-   situations with popular items. [benja says: This is not related
-   to the central point as expressed in the title; therefore, I believe
-   it should be given as a benefit of the system somewhere later
-   in the paper (like many others) but not put here...]
 
 Advanced hypermedia systems such as Microcosm and Hyper-G
 address dangling links through a notification system: