1129 |
agreed with benja on irc that we might try this approach - hinting about the |
agreed with benja on irc that we might try this approach - hinting about the |
1130 |
use cases early on and taking a detailed look later, in light of the design.) |
use cases early on and taking a detailed look later, in light of the design.) |
1131 |
|
|
1132 |
|
evaluation |
1133 |
|
---------- |
1134 |
|
|
1135 |
|
To evaluate the design, the issues raised by data mobility are revisited in |
1136 |
|
the following. For the two issues addressed, *danglink links* and *tracking |
1137 |
|
alternative versions*, each individual (use) case that was identified in the |
1138 |
|
introduction is used here to illustrate Storm. |
1139 |
|
|
1140 |
|
*Dangling links*. When documents are moved between servers, when using Storm |
1141 |
|
the links to them are not affected as the identifiers are |
1142 |
|
location-independent. In a peer-to-peer implementation, the lookup with the |
1143 |
|
id returns a location where the data is currently available. If the |
1144 |
|
publisher removes the document permanently, but it is archived elsewhere, |
1145 |
|
the archives act as peers similarly. When there is no network connection |
1146 |
|
available, but a local copy instead, the lookup points to that. |
1147 |
|
|
1148 |
1. live meeting: |
1. live meeting: |
1149 |
Documents have been assigned block-ids (and urns?) at creation. |
Documents have been assigned block-ids (and urns?) at creation. |
1150 |
Pools that are shared / set visible for the other user show over the |
Pools that are shared / set visible for the other user show over the |