[Gzz-commits] manuscripts/storm article.rst

[Toni Alatalo]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Toni Alatalo <address@hidden>   03/02/06 08:27:21

Modified files:
        storm          : article.rst 

Log message:
        some misc. work

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/storm/article.rst.diff?tr1=1.105&tr2=1.106&r1=text&r2=text

Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.105 manuscripts/storm/article.rst:1.106
--- manuscripts/storm/article.rst:1.105 Thu Feb  6 07:18:07 2003
+++ manuscripts/storm/article.rst       Thu Feb  6 08:27:21 2003
@@ -119,7 +119,7 @@
 .. [General figure of Storm, i.e. application layer, storm layer, 
    netowork layer ? -Hermanni]
  
-.. [Move somewhere else -b]:
+.. [Move somewhere else -b]::
    [Section 8 ?-) -Hermanni]
    No work on integrating Storm with current programs (in the spirit of Open 
Hypermedia)
    has been done so far. It is not clear how far this is possible
@@ -131,7 +131,7 @@
 .. Investigating the degrees of interoperability with Open Hypermedia
    (/Structural Computing?) and (more primitive?) other (Web) XXX is a possible
    direction for future work, and will be preliminarly discussed here too.
-   [benja says: Really? Do we/can we discuss that really?]
+   [benja says: Really? Do we/can we discuss that really? antont: 'll try.]
 
 This paper is structured as follows. In the next section, we describe 
 related work. In section 3, we introduce the basic storage unit of our 
@@ -145,12 +145,8 @@
 we report on implementation experience and future directions. 
 Section 9 concludes the paper.
 
-.. (where and how use cases? are not mentioned in either of the above, but are
-   currently split in two - hinting somewhere in the beginning and reviewing at
-   the and).
-   [In appendix A ? -Hermanni]
-   [IMHO: Use cases in intro, discussion on how Storm applies to them
-   to the end/in Conclusions. -b]
+.. [Use cases in intro, discussion on how Storm applies to them
+   to the end/in Conclusions.]
 
 
 2. Related Work
@@ -218,7 +214,7 @@
 architecture. Groove [ref] is a improved design of Lotus Notes, which employs 
 strong security mechanisms and uses peer-to-peer functionality 
 as basis of communication channel among limited amount of participants. 
-Neither of these systems don't support the immutable of data.
+Neither of these systems supports the immutability of data.
 
 CFS [ref], which is built upon Chord DHT peer-to-peer routing layer[ref], 
stores 
 data as blocks. However, CFS *splits* data (files) into several miniblocks and 
@@ -463,7 +459,7 @@
 
 Our current implementation shows only links between documents
 that are in memory at the same time [screenshot of xupdf, perhaps ref too
-(submitted) ?].
+(submitted) antont: was thinking the same, it would illustrate this well].
 In the future, we will implement a global distributed index at top of
 a distributed hashtable, with the scroll blocks' ids as the keys.
 To find the transclusions of a span, the system will retrieve
@@ -477,6 +473,8 @@
 that this will not be a major scalability problem. Otherwise,
 systems that allow range queries, such as skip graphs [ref] 
 and skipnet [ref], may prove useful.
+[how does video work here, i.e. are they huge blocks or collections of many
+small, frames? or a sequence between two keyframes?]
 
 [This might be relevant also:
 http://www.hpl.hp.com/techreports/2002/HPL-2002-209.pdf
@@ -485,7 +483,7 @@
 One question raised by xanalogical storage is which links to show
 for a popular document that has been linked to by many users.
 We hope to address this problem by collaborative filtering
-of links [explain, ref]. There has been research on
+of links [explain, ref (grouplens.org pubs?)]. There has been research on
 collaborative filtering in peer-to-peer systems
 without compromising participants' privacy [ref John Canny].
 
@@ -514,11 +512,12 @@
 
     getMappings(block) -> set of (key, value) pairs
 
-.. [What is mapping ? We should explain this :) -Hermanni]
+.. [What is mapping ? We should explain this :) -Hermanni
+       isn't it explained above? it's a set of key-value pairs]
 
 This callback processes a block and returns a set of mappings
 to be placed into the index. The Storm pool, in turn, provides 
-the following interface to the application::
+the following interface to the application:
 
     get(key) -> set of (block, value) pairs
 
@@ -890,7 +889,7 @@
 and verify offline that it really comes from NYT. How to do this will go
 into the article as an open research question ;-)
 
-Future directions: of course, we shoul implement a prototype
+Future directions: of course, we should implement a prototype
 
 Open issue/Future directions: implement multisource downloading
 
@@ -899,6 +898,13 @@
 Open issue: Firewall Transparency/NATs ?
 
 Open issue: identification of online entities ? 
+
+Open issue: how to address interoperability - what do we mean with it?
+One thing might be to look at the OHS OHProtocol and such.
+Another is to investigate Web publishing with using storm for zope?
+interestingly zope by default stores diffs in the zodb (similarly:cvs&storm?)
+Benja also noted about pointing to external data? (couldn't find the post
+from the archives)
 
 9. Conclusions
 ==============