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 18:53:08 -0500

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

Modified files:
        storm          : article.rst 

Log message:
        org use cases

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

Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.94 manuscripts/storm/article.rst:1.95
--- manuscripts/storm/article.rst:1.94  Wed Feb  5 18:44:25 2003
+++ manuscripts/storm/article.rst       Wed Feb  5 18:53:07 2003
@@ -67,18 +67,23 @@
 or on the local computer (after being downloaded and stored
 locally). In particular, the latter is important for off-line work
 (on a laptop or dialup system).
-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. 
-
-Dangling links are an issue for unpublished documents
+For unpublished documents, dangling links are an issue
 when a document and a link to it are received independently
 (for example, as attachments to different emails, possibly
-from different senders). In the future, [XXX train collaboration].
+from different senders). In the future, they may be an issue (XXX why)
+for ad-hoc sharing, for example when two people meet on the train
+and want to exchange documents they have stored locally
+[ref Thompton et al].
+
 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 
+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:




reply via email to

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