/[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.91 by benja, Wed Feb 5 22:05:04 2003 UTC revision 1.92 by benja, Wed Feb 5 22:40:01 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:
64    
65    - train collaboration
66    - email attachment synchronization of versions
67    - publication, hosting on own computer
68    - comments and links on published document
69    - travelling with laptop, off-line work
70    - load
71    - reconnecting the laptop after off-line work
72    
73  .. The design also allows for  .. The design also allows for
74     automatic balancing of the load, which occurs in location-dependent     automatic balancing of the load, which occurs in location-dependent
75     situations with popular items. [benja says: This is not related     situations with popular items. [benja says: This is not related
# Line 74  Hyper-G uses an efficient protocol for d Line 84  Hyper-G uses an efficient protocol for d
84  on the public Internet.  on the public Internet.
85    
86  Location-independent identifiers for documents  Location-independent identifiers for documents
87  make such a notification unnecessary; a peer-to-peer lookup system  make such notification unnecessary; a peer-to-peer lookup system
88  can resolve them whereever the documents are moved.  can resolve them whereever the documents are moved.
89  Such a system also works for data not publicized on the Internet.  Such a system also works for data not publicized on the Internet.
90  For example, if one email has a document attached to it, and another email  For example, if one email has a document attached to it, and another email
# Line 83  by permanent identifier allows the syste Line 93  by permanent identifier allows the syste
93  This would be extremely difficult to realize through a  This would be extremely difficult to realize through a
94  notification mechanism like Microcosm's and Hyper-G's.  notification mechanism like Microcosm's and Hyper-G's.
95    
 XXX use cases  
   
96  In this paper, we present Storm (for *storage module*), a design  In this paper, we present Storm (for *storage module*), a design
97  dealing with these issues. Storm is a library  dealing with these issues. Storm is a library
98  for storing and retrieving data as immutable  for storing and retrieving data as immutable
# Line 119  and an implementation of Xanalogical sto Line 127  and an implementation of Xanalogical sto
127     direction for future work, and will be preliminarly discussed here too.     direction for future work, and will be preliminarly discussed here too.
128     [benja says: Really? Do we/can we discuss that really?]     [benja says: Really? Do we/can we discuss that really?]
129    
130  This paper is structured as follows. In next section, we describe  This paper is structured as follows. In the next section, we describe
131  related work. In section 3, we introduce the basic storage unit of our  related work. In section 3, we introduce the basic storage unit of our
132  system, file-like blocks of data identified by cryptographic hashes.  system, file-like blocks of data identified by cryptographic hashes.
133  In section 4, we discuss our implementation of Xanalogical storage  In section 4, we discuss our implementation of Xanalogical storage

Legend:
Removed from v.1.91  
changed lines
  Added in v.1.92

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