170 |
As opposed to filesystems, Storm uses |
As opposed to filesystems, Storm uses |
171 |
uses Freenet-like cryptographic identifiers to |
uses Freenet-like cryptographic identifiers to |
172 |
manipulate the blocks. |
manipulate the blocks. |
173 |
This seems like a bad tradeoff: while these identifiers |
This may seem like a bad tradeoff: while these identifiers |
174 |
enable secure location-independent references, they |
enable secure location-independent references, they |
175 |
do not allow |
do not allow |
176 |
the documents referred to by the identifiers to change |
the documents referred to by the identifiers to change |
177 |
and |
and |
178 |
are also less comprehensible for humans. |
are also less comprehensible for humans. |
179 |
However, Storm is able to address both downsides by |
However, these downsides are dealt with by the higher abstraction |
180 |
simple cryptographic techniques. |
levels |
181 |
|
of Storm. |
182 |
|
|
183 |
.. pointers |
.. pointers |
184 |
|
|
185 |
One of the key innovations in storm is the use |
One of the key innovations in Storm is the use |
186 |
of *pointer blocks* |
of *pointer blocks* |
187 |
to build mutable documents on top of |
to build mutable documents on top of |
188 |
the lowest layer append-and-delete-only model. |
the lowest layer append-and-delete-only model. |
283 |
to all other documents referred to by the same pointer, |
to all other documents referred to by the same pointer, |
284 |
i.e. links to *alternate* or *earlier* versions of the document. |
i.e. links to *alternate* or *earlier* versions of the document. |
285 |
|
|
286 |
|
The most important downside of using Storm in lieu of file names and URLs |
287 |
|
is the long, cryptic URIs which |
288 |
|
would ideally be handled through some user interface changes |
289 |
|
to the file selector dialog boxes. |
290 |
|
|
291 |
Conclusions |
Conclusions |
292 |
=========== |
=========== |
295 |
the namespaces for private and published documents. |
the namespaces for private and published documents. |
296 |
This may help in making hyperlinks between desktop |
This may help in making hyperlinks between desktop |
297 |
documents more convenient. |
documents more convenient. |
|
|
|
|
XXX CURRENT INTERFACING |
|
|
The downside is the long, cryptic URIs which |
|
|
would ideally be handled through some user interface changes |
|
|
CUTTING&PASTING. |
|
|
|
|
|
A distributed hashtable is used to locate published documents |
|
|
on a global state. |
|
298 |
While the core of Storm has been in use for almost |
While the core of Storm has been in use for almost |
299 |
three years, the peer-to-peer subsystem has only recently |
three years, the peer-to-peer subsystem has only recently |
300 |
been implemented. |
been implemented. |
301 |
Currently, a number of systems can use Storm |
Currently, a number of systems can use Storm |
302 |
through an HTTP gateway. |
through an HTTP gateway or the KDE libraries. |
303 |
|
Storm can also be used to implement the more ambitious |
304 |
XXX WHAT IS THE CONTRIBUTION OVER FREENET, GNUTELLA ... |
Xanalogical hypertext model [#]_ [lukka02guids]_. |
305 |
|
Storm is available as Free Software from |
306 |
|
``http://sv.gnu.org/projects/storm``. |
307 |
|
|
308 |
XXX Chief contributions of storm: pointers, ...?? |
The main new features in Storm over previous systems |
309 |
|
are the integration of |
310 |
|
ordinary office applications with the P2P network and |
311 |
|
pointer blocks which allow basic versioning of documents. |
312 |
|
|
313 |
|
Storm is by no means finished: more work is needed |
314 |
|
on, e.g., versioning when a group of people are |
315 |
|
collaborating on a document, i.e., when the pointer is not |
316 |
|
associated with only one person. |
317 |
|
|
318 |
XXX Authentication, user management needs work |
.. A distributed hashtable is used to locate published documents |
319 |
|
on a global scale. |
320 |
|
|
321 |
.. A next step will be |
.. A next step will be |
322 |
WebDAV support, allowing many more systems to |
WebDAV support, allowing many more systems to |
323 |
save data in Storm. |
save data in Storm. |
324 |
|
|
|
Storm can also be used to implement the more ambitious |
|
|
Xanalogical hypertext model [#]_ [lukka02guids]_. |
|
|
Storm is available as Free Software from |
|
|
``http://sv.gnu.org/projects/storm``. |
|
|
|
|
325 |
.. [#] Our implementation of Xanalogical storage |
.. [#] Our implementation of Xanalogical storage |
326 |
is available at ``http://sv.gnu.org/projects/alph``. |
is available at ``http://sv.gnu.org/projects/alph``. |
327 |
|
|