/[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.141 by antont, Thu Feb 13 13:30:37 2003 UTC revision 1.142 by hemppah, Thu Feb 13 13:48:08 2003 UTC
# Line 40  distributed hashtables, DHT Line 40  distributed hashtables, DHT
40  ===============  ===============
41    
42  The Web and many other hypermedia systems assume that identifiers  The Web and many other hypermedia systems assume that identifiers
43  either have to include location information (as in URLs, which break  either have to include location information (as in regular URLs, which break
44  when documents are moved), or can only be resolved locally (as in  when documents are moved), or can only be resolved locally (as in
45  link services that can only find links stored on a select set  link services that can only find links stored on a select set
46  of link servers [ref Microcosm, DLS, ...]). Berners-Lee [ref NameMyth - that  of link servers [ref Microcosm, DLS, ...]). Berners-Lee [ref NameMyth - that
# Line 52  rendered this assumption obsolete. Struc Line 52  rendered this assumption obsolete. Struc
52  [ref chord, can, tapestry, pastry, kademlia, symphony, viceroy,  [ref chord, can, tapestry, pastry, kademlia, symphony, viceroy,
53  skip graph, swan, kelips] allow location-independent identifiers  skip graph, swan, kelips] allow location-independent identifiers
54  to be resolved on a global scale.  to be resolved on a global scale.
55  Thus, it is now feasible to do a global search to find all information  Thus, it is now possible to perform a global lookup to find all information
56  related to a given identifier on any participating peer in the network.  related to a given identifier on any participating peer in the network.
57  This, we believe, may be the most important result of peer-to-peer  This, we believe, may be the most important result of peer-to-peer
58  research with regard to hypermedia.  research with regard to hypermedia.
59    
60  We examine how location-independent identifiers can support *data mobility*.  In this paper, we examine how location-independent identifiers can
61  In today's computing world, documents move quite freely between  support *data mobility*. Our motivation has been inspired by today's computing
62  computers: they are sent as e-mail attachments, carried around on disks,  world, in which documents move quite freely between computers: they are sent as
63  published on the web, moved between desktop and laptop systems,  e-mail attachments, carried around on disks, published on the web, moved
64  downloaded for off-line reading or copied between computers in a LAN.  between desktop and laptop systems, downloaded for off-line reading or
65  We use 'data mobility' as a collective term for the movement of documents  copied between computers in a LAN. We use 'data mobility' as a collective
66  between computers (or folders!),  term for the movement of documents between computers (or folders!),
67  and movement of content between documents (through copy&paste) [#]_.  and movement of content between documents (through copy&paste) [#]_.
68    
69  .. [#] While the physical mobility of e.g. notebooks may effect  .. [#] While the physical mobility of e.g. notebooks may effect
# Line 71  and movement of content between document Line 71  and movement of content between document
71     data mobility is neither the same as, nor limited to the physical     data mobility is neither the same as, nor limited to the physical
72     movement of devices.     movement of devices.
73    
74  In this paper, we address two issues raised by data mobility:  We address two issues raised by data mobility:
75  Dangling links and keeping track of alternative versions.  Dangling links and keeping track of alternative versions.
76  Resolvable location-independent identifiers  Resolvable location-independent identifiers
77  make these issues much easier to deal with, since data  make these issues much easier to deal with, since data
# Line 1272  collabaration (irc?)? Line 1272  collabaration (irc?)?
1272  8. Conclusions  8. Conclusions
1273  ==============  ==============
1274    
1275  We have presented the Storm design, which makes use of recent advances  We have addressed two important issues raised by data mobility, dangling
1276  in peer-to-peer technology to support many different forms  links and keeping track of alternative versions. Moreover, we have presented
1277  of data mobility. All data is stored in immutable blocks,  the Storm design, which makes use of recent advances in peer-to-peer technology
1278  of which application-specific indices can be kept. On top of  to resolve these issues.  In Storm, all data is stored as immutable blocks and
1279  indexed blocks, we implement efficient versioned storage  each block has globally unique identifier. Application-specific indices can be kept
1280  of mutable resources as well as Xanalogical storage.  of these blocks. On top of indexed blocks, we have implemented efficient versioned
1281    storage of mutable resources as well as Xanalogical storage.
1282  Storm is not limited to network publishing;  
1283  it is intended to be used for private documents stored on  Storm is not only limited to network publishing;
1284  desktop systems as well. Our current implementation does not support  it can be also used for private document repository. Our current implementation
1285  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
1286  for local storage and server-based collaboration  for local storage and server-based collaboration for one and a half years.
 for one and a half years.  
1287    
1288  Storm has proven to be a solid basis for Gzz, but  Storm has proven to be a solid basis for Gzz, but
1289  no work has been done to integrate it with existing systems, yet.  no work has been done to integrate it with existing systems, yet.

Legend:
Removed from v.1.141  
changed lines
  Added in v.1.142

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