1092 |
allow us to download parts of a block from multiple sources |
allow us to download parts of a block from multiple sources |
1093 |
simultaneously (as in e.g. [XXX ref Overnet]). |
simultaneously (as in e.g. [XXX ref Overnet]). |
1094 |
|
|
|
Storm has proven to be a solid basis for Gzz, but |
|
|
no work has been done to integrate it with existing systems, yet. |
|
|
This makes Storm a rather monolithic approach at present. |
|
|
However, even if Storm-- or especially Xanalogical storage-- |
|
|
should be hard to integrate with existing systems, |
|
|
we believe that it is valuable as an exercise in what is possible |
|
|
if we can break backwards compatibility with the state of the art. |
|
|
|
|
1095 |
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 |
1096 |
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 |
1097 |
without changing applications substantially, if advantage of our |
without changing applications substantially, if advantage of our |
1098 |
implementation of Xanalogical storage is to be taken. Vitali [vitali99versioning]_ |
implementation of Xanalogical storage is to be taken. Vitali [vitali99versioning]_ |
1099 |
notes that Xanalogical storage necessiates strong discipline in version tracking, |
notes that Xanalogical storage necessiates strong discipline in version tracking, |
1100 |
which current systems lack. One possibility is to take an existing system |
which current systems lack. |
1101 |
|
This makes Storm a rather monolithic approach at present. |
1102 |
|
|
1103 |
|
One possibility is to take an existing system |
1104 |
(with features outside the focus of Gzz) |
(with features outside the focus of Gzz) |
1105 |
that implements strict versioning, and to modify it to use Storm for storage. |
that implements strict versioning, and to modify it to use Storm for storage. |
1106 |
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, |
1112 |
as well -- for example the conventions for listing, moving and deleting |
as well -- for example the conventions for listing, moving and deleting |
1113 |
blocks. |
blocks. |
1114 |
|
|
1115 |
At the end, we hope that we have provided a case study in |
We have provided a case study in |
1116 |
what's possible in a system that does not use |
what's possible in a system that does not use |
1117 |
location-dependent identifiers at all. We hope to raise awareness |
location-dependent identifiers at all. We hope to raise awareness |
1118 |
for the prospects of location-independent systems based |
for the prospects of location-independent systems based |