44 |
computers: being sent as e-mail attachments, carried around on disks, |
computers: being sent as e-mail attachments, carried around on disks, |
45 |
published on the web, moved between desktop and laptop systems, |
published on the web, moved between desktop and laptop systems, |
46 |
downloaded for off-line reading or copied between computers in a LAN. |
downloaded for off-line reading or copied between computers in a LAN. |
47 |
Furthermore, the same document is independently modified |
Furthermore, the same document may be independently modified |
48 |
on two (or more) unconnected, separete systems. We use |
on two (or more) unconnected, separete systems. We use |
49 |
*data mobility* as a collective term for the movement of documents |
*data mobility* as a collective term for the movement of documents |
50 |
between computers (or locations on one computer, such as folders), |
between computers (or locations on one computer, such as folders), |
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: |
Examples for data mobility include today: |
64 |
|
|
65 |
- train collaboration |
- sharing versions (email attachment, disk) -> versioning |
66 |
- email attachment synchronization of versions |
- cvs-like central sync point(s) -> versioning |
67 |
- publication, hosting on own computer |
- off-line work (dialup, laptop/cellphone/pda) -> links |
68 |
- comments and links on published document |
- publication -> links |
69 |
- travelling with laptop, off-line work |
- mirroring -> links |
70 |
- load |
- downloading -> links, versioning if modified after download |
71 |
- reconnecting the laptop after off-line work |
- moving between own systems (desktop/laptop, work/home) -> |
72 |
|
versioning, links |
73 |
|
- web archive -> links, versioning (past versions) |
74 |
|
|
75 |
|
Future visions: |
76 |
|
|
77 |
|
- downloading from others' cache/permanent storage (load balancing) -> |
78 |
|
links |
79 |
|
- hosting on own computer. others mirror -> links |
80 |
|
- ad-hoc sharing (train, cafe) -> links |
81 |
|
|
82 |
|
.. not really data mobility: |
83 |
|
- comments and links on published document |
84 |
|
|
85 |
.. The design also allows for |
.. The design also allows for |
86 |
automatic balancing of the load, which occurs in location-dependent |
automatic balancing of the load, which occurs in location-dependent |
123 |
On top of Storm, we have built a system for storing mutable, versioned data |
On top of Storm, we have built a system for storing mutable, versioned data |
124 |
and an implementation of Xanalogical storage [ref]. |
and an implementation of Xanalogical storage [ref]. |
125 |
|
|
126 |
|
XXX {The current implementation has been used for local disk storage |
127 |
|
and central sync point. Our p2p impl is in a very early stage, and |
128 |
|
we have not yet implemented ad-hoc sharing (aka train collaboration).] |
129 |
|
|
130 |
.. [General figure of Storm, i.e. application layer, storm layer, |
.. [General figure of Storm, i.e. application layer, storm layer, |
131 |
netowork layer ? -Hermanni] |
netowork layer ? -Hermanni] |
132 |
|
|