/[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.88 by benja, Wed Feb 5 21:32:17 2003 UTC revision 1.89 by benja, Wed Feb 5 21:43:32 2003 UTC
# Line 113  project [ref], which uses Storm exclusiv Line 113  project [ref], which uses Storm exclusiv
113  Gzz provides a general platform for building hypermedia applications upon.  Gzz provides a general platform for building hypermedia applications upon.
114  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
115  and an implementation of Xanalogical storage [ref].  and an implementation of Xanalogical storage [ref].
116  [General figure of Storm, i.e. application layer, storm layer,  
117  netowork layer ? -Hermanni]  .. [General figure of Storm, i.e. application layer, storm layer,
118       netowork layer ? -Hermanni]
119    
120  No work on integrating Storm with current programs (in the spirit of Open Hypermedia)  No work on integrating Storm with current programs (in the spirit of Open Hypermedia)
121  has been done so far. It is not clear how far this is possible  has been done so far. It is not clear how far this is possible
# Line 122  without changing applications substantia Line 123  without changing applications substantia
123  of our implementation of Xanalogical storage is to be taken.  of our implementation of Xanalogical storage is to be taken.
124  (Vitali [ref] notes that Xanalogical storage necessiates  (Vitali [ref] notes that Xanalogical storage necessiates
125  strong discipline in version tracking, which current systems lack.)  strong discipline in version tracking, which current systems lack.)
126  Investigating the degrees of interoperability with Open Hypermedia  
127  (/Structural Computing?) and (more primitive?) other (Web) XXX is a possible  .. Investigating the degrees of interoperability with Open Hypermedia
128  direction for future work, and will be preliminarly discussed here too.     (/Structural Computing?) and (more primitive?) other (Web) XXX is a possible
129  [benja says: Really? Do we/can we discuss that really?]     direction for future work, and will be preliminarly discussed here too.
130       [benja says: Really? Do we/can we discuss that really?]
131    
132  This paper is structured as follows. In next section, we describe  This paper is structured as follows. In next section, we describe
133  related work. In section 3, we introduce the basic storage unit of our  related work. In section 3, we introduce the basic storage unit of our
# Line 139  potential peer-to-peer implementations o Line 141  potential peer-to-peer implementations o
141  we report on implementation experience and future directions.  we report on implementation experience and future directions.
142  Section 9 concludes the paper.  Section 9 concludes the paper.
143    
144  (where and how use cases? are not mentioned in either of the above, but are  .. (where and how use cases? are not mentioned in either of the above, but are
145  currently split in two - hinting somewhere in the beginning and reviewing at     currently split in two - hinting somewhere in the beginning and reviewing at
146  the and).     the and).
147  [In appendix A ? -Hermanni]     [In appendix A ? -Hermanni]
148  [IMHO: Use cases in intro, discussion on how Storm applies to them     [IMHO: Use cases in intro, discussion on how Storm applies to them
149  to the end/in Conclusions. -b]     to the end/in Conclusions. -b]
150    
151    
152  2. Related Work  2. Related Work
# Line 438  and the characters retrieved from there Line 440  and the characters retrieved from there
440    
441  Our current implementation shows only links between documents  Our current implementation shows only links between documents
442  that are in memory at the same time [screenshot of xupdf, perhaps ref too  that are in memory at the same time [screenshot of xupdf, perhaps ref too
443   (submitted) ?].  (submitted) ?].
444  In the future, we will implement a global distributed index at top of  In the future, we will implement a global distributed index at top of
445  a distributed hashtable, with the scroll blocks' ids as the keys.  a distributed hashtable, with the scroll blocks' ids as the keys.
446  To find the transclusions of a span, the system will retrieve  To find the transclusions of a span, the system will retrieve
# Line 487  mappings into the index. Instead, applic Line 489  mappings into the index. Instead, applic
489  to index blocks provide the following callback  to index blocks provide the following callback
490  to a Storm pool::  to a Storm pool::
491    
 [What is mapping ? We should explain this :) -Hermanni]  
   
492      getMappings(block) -> set of (key, value) pairs      getMappings(block) -> set of (key, value) pairs
493    
494    .. [What is mapping ? We should explain this :) -Hermanni]
495    
496  This callback processes a block and returns a set of mappings  This callback processes a block and returns a set of mappings
497  to be placed into the index. The Storm pool, in turn, provides  to be placed into the index. The Storm pool, in turn, provides
498  the following interface to the application::  the following interface to the application::

Legend:
Removed from v.1.88  
changed lines
  Added in v.1.89

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