/[gzz]/manuscripts/storm/article.rst
ViewVC logotype

Diff of /manuscripts/storm/article.rst

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.93 by benja, Wed Feb 5 22:57:10 2003 UTC revision 1.94 by benja, Wed Feb 5 23:44:25 2003 UTC
# Line 60  Resolvable location independent identifi Line 60  Resolvable location independent identifi
60  make these issues much easier to deal with, since data  make these issues much easier to deal with, since data
61  can be recognized whereever it is moved.  can be recognized whereever it is moved.
62    
63  Examples for data mobility include today:  Dangling links are an issue for published documents
64    when data is moved between servers, and
65    when documents are removed by the original publisher, but
66    copies still exist in the network (e.g. in the web archive [ref])
67    or on the local computer (after being downloaded and stored
68    locally). In particular, the latter is important for off-line work
69    (on a laptop or dialup system).
70    Efficiency can be improved if documents can
71    be found on the local machine if they have been cached or downloaded,
72    or from any peer that has a copy in its cache.
73    
74    Dangling links are an issue for unpublished documents
75    when a document and a link to it are received independently
76    (for example, as attachments to different emails, possibly
77    from different senders). In the future, [XXX train collaboration].
78    Also, after a document is published, local backlinks to it
79    should be shown together along with public backlinks made by others.
80    
81    Alternate versions are an issue when
82    
83    
84    .. Examples for data mobility include today:
85    
86       - sharing versions (email attachment, disk) -> versioning
87       - cvs-like central sync point(s) -> versioning
88       - off-line work (dialup, laptop/cellphone/pda) -> links
89       - publication -> links
90       - mirroring -> links
91       - downloading -> links, versioning if modified after download
92       - moving between own systems (desktop/laptop, work/home) ->
93         versioning, links
94       - web archive -> links, versioning (past versions)
95    
96       Future visions:
97    
98       - downloading from others' cache/permanent storage (load balancing) ->
99         links
100       - hosting on own computer. others mirror -> links
101       - ad-hoc sharing (train, cafe) -> links
102    
103  - sharing versions (email attachment, disk) -> versioning     Not really data mobility:
 - 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  
104    
 .. not really data mobility:  
105     - comments and links on published document     - comments and links on published document
106    
107  .. The design also allows for  .. The design also allows for

Legend:
Removed from v.1.93  
changed lines
  Added in v.1.94

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26