/[gzz]/manuscripts/storm/article.rst
ViewVC logotype

Diff of /manuscripts/storm/article.rst

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.187 by benja, Sat Feb 15 17:43:40 2003 UTC revision 1.188 by benja, Sat Feb 15 17:56:58 2003 UTC
# Line 1082  We have introduced the Storm design to a Line 1082  We have introduced the Storm design to a
1082  raised by data mobility, dangling links and keeping track  raised by data mobility, dangling links and keeping track
1083  of alternative versions. In Storm, all data is stored as immutable blocks  of alternative versions. In Storm, all data is stored as immutable blocks
1084  identified a SHA-1 hash. Application-specific indices of these blocks can be kept.  identified a SHA-1 hash. Application-specific indices of these blocks can be kept.
1085  On top of indexed blocks, we have implemented efficient versioned  On top of indexed blocks, we have implemented 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 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 present 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 a GISP-based peer-to-peer
1093  implementation of Storm. In the future, we intend to explore  implementation.
 other DHT implementations, too.  
1094    
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 yet. This may be difficult with Xanalogical
1097  without changing applications substantially, if advantage of our  storage; Vitali [vitali99versioning]_
 implementation of Xanalogical storage is to be taken. Vitali [vitali99versioning]_  
1098  notes that Xanalogical storage necessiates strong discipline in version tracking,  notes that Xanalogical storage necessiates strong discipline in version tracking,
1099  which current systems lack.  which current systems lack.
1100  This makes Storm a rather monolithic approach at present.  This makes Storm a rather monolithic approach at present.
# Line 1105  One possibility is to take an existing s Line 1103  One possibility is to take an existing s
1103  (with features outside the focus of Gzz)  (with features outside the focus of Gzz)
1104  which 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.
1105  A candidate is the object-oriented Web publishing environment Zope [zope]_,  A candidate is the object-oriented Web publishing environment Zope [zope]_,
1106  which is Free Software and stores everything by default as diffs to  which is Free Software. The
 a (flat file) database. The  
1107  open hypermedia protocol (OHP) may be another possibiliy [reich-davis99-ohp].  open hypermedia protocol (OHP) may be another possibiliy [reich-davis99-ohp].
1108    
1109  Besides these issues with the backend, we are facing user interface issues  Work is also needed on user interfaces for Storm.
 as well -- for example the conventions for listing, moving and deleting  
 blocks.  
1110    
1111  .. Also conventions for which zones e.g. new blocks should be stored in  .. Besides these issues with the backend, we are facing user interface issues
1112       as well -- for example the conventions for listing, moving and deleting
1113       blocks. Also conventions for which zones e.g. new blocks should be stored in
1114     must be resolved. Often they will be private, but when making changes to     must be resolved. Often they will be private, but when making changes to
1115     documents that are shared with a project group, the changes should be     documents that are shared with a project group, the changes should be
1116     visible to others.     visible to others.
1117    
1118  We have provided a case study in  We see Storm as a case study in
1119  what's possible in a system that does not use  the potentials of a system that does not use
1120  location-dependent identifiers at all. We hope to raise awareness  location-dependent identifiers at all. We hope to raise awareness
1121  for the prospects of location-independent systems based  for the prospects of location-independent systems based
1122  on structured overlay networks such as DHTs.  on structured overlay networks such as DHTs.

Legend:
Removed from v.1.187  
changed lines
  Added in v.1.188

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26