30 |
downloaded for off-line reading or copied between computers in a LAN. |
downloaded for off-line reading or copied between computers in a LAN. |
31 |
Often, the same document is independently modified |
Often, the same document is independently modified |
32 |
on two more more unconnected, separete systems. We address two issues |
on two more more unconnected, separete systems. We address two issues |
33 |
raised by this *data mobility* phenomenon: Dangling links, and keeping track |
raised by this ad hoc *data mobility* (see footnote) phenomenon: Dangling links, |
34 |
of alternative versions. Resolvable location independent identifiers |
and keeping track of alternative versions. Resolvable location independent identifiers |
35 |
make these issues much easier to deal with, since data |
make these issues much easier to deal with, since data |
36 |
can be recognized whereever it is moved. |
can be recognized whereever it is moved. |
37 |
|
|
38 |
|
footnote: we emphasize the mobility of *data*. Indeed, technology used |
39 |
|
for moving data is not our primary concern. |
40 |
|
|
41 |
In this paper, we present Storm (for *storage module*), a design |
In this paper, we present Storm (for *storage module*), a design |
42 |
for dealing with these issues. Storm provides an interface to |
for dealing with these issues. Storm provides an interface to |
43 |
applications for storing and retrieving data in immutable |
applications for storing and retrieving data in immutable |