1078 |
Conclusions |
Conclusions |
1079 |
=========== |
=========== |
1080 |
|
|
1081 |
We have addressed two important issues raised by data mobility, dangling |
We have introduced the Storm design to address two important issues |
1082 |
links and keeping track of alternative versions. Moreover, we have presented |
raised by data mobility, dangling links and keeping track |
1083 |
the Storm design, which makes use of recent advances in peer-to-peer technology |
of alternative versions. In Storm, all data is stored as immutable blocks |
1084 |
to resolve these issues. In Storm, all data is stored as immutable blocks and |
identified a SHA-1 hash. Application-specific indices of these blocks can be kept. |
1085 |
each block has globally unique identifier. Application-specific indices can be kept |
On top of indexed blocks, we have implemented efficient versioned |
|
of these blocks. On top of indexed blocks, we have implemented efficient versioned |
|
1086 |
storage of mutable resources as well as Xanalogical storage. |
storage of mutable resources as well as Xanalogical storage. |
1087 |
|
|
1088 |
Storm is not only limited to network publishing; |
Storm is not limited to network publishing; |
1089 |
it can be also used for private document repository. Our current implementation |
it can be also used for private document repository. Our current implementation |
1090 |
does not support peer-to-peer distribution yet, but the Gzz project has used it |
does not support peer-to-peer distribution yet, but the Gzz project has used it |
1091 |
for local storage and server-based collaboration for one and a half years. |
for local storage and server-based collaboration for one and a half years. |
|
|
|
1092 |
Currently, we are working on completing our GISP-based peer-to-peer |
Currently, we are working on completing our GISP-based peer-to-peer |
1093 |
implementation of Storm. Once this is done, we intend to explore |
implementation of Storm. In the future, we intend to explore |
1094 |
alternative DHT implementations as well. We will also evaluate |
other DHT implementations, too. |
|
using Merkle hash trees [XXXref] to identify blocks; this would |
|
|
allow us to download parts of a block from multiple sources |
|
|
simultaneously (as in e.g. [XXX ref Overnet]). |
|
1095 |
|
|
1096 |
No work on integrating Storm with current programs (in the spirit of Open |
No work on integrating Storm with current programs (in the spirit of Open |
1097 |
Hypermedia) has been done so far. It is not clear how far this is possible |
Hypermedia) has been done so far. It is not clear how far this is possible |
1103 |
|
|
1104 |
One possibility is to take an existing system |
One possibility is to take an existing system |
1105 |
(with features outside the focus of Gzz) |
(with features outside the focus of Gzz) |
1106 |
that implements strict versioning, and to modify it to use Storm for storage. |
which implements strict versioning, and to modify it to use Storm for storage. |
1107 |
A candidate is the object-oriented (web) publishing environment Zope [ref zope.org/com, book, |
A candidate is the object-oriented Web publishing environment Zope [ref zope.org/com, book, |
1108 |
article?], which is Free Software and stores everything by default as diffs to |
article?], which is Free Software and stores everything by default as diffs to |
1109 |
a (flat file) database. Another way is studying the applicability of the |
a (flat file) database. Another way is studying the applicability of the |
1110 |
open hypermedia protocol (OHP) [reich-davis99-ohp]. |
open hypermedia protocol (OHP) [reich-davis99-ohp]. |