12 |
.. We argue that while non-breaking links would be a convenience |
.. We argue that while non-breaking links would be a convenience |
13 |
on the Web, they are a necessity for making Web-like hyperlinks |
on the Web, they are a necessity for making Web-like hyperlinks |
14 |
useful on the local desktop. |
useful on the local desktop. |
15 |
|
|
16 |
|
.. My suggestion for starting abstract: |
17 |
|
Linking personal documents like we link Web pages is inconvenient |
18 |
|
enough that users rarely ever do it. |
19 |
|
We argue that while non-breaking links would be a convenience |
20 |
|
on the Web, they are a necessity for making Web-like hyperlinks |
21 |
|
useful on the local desktop. (move "A major reason..." to intro ?) [HH] |
22 |
|
|
23 |
We propose Storm, a storage system for use both on the |
We propose Storm, a storage system for use both on the |
24 |
desktop and the public network. Storm assigns each document |
desktop and the public network. Storm assigns each document |
25 |
a permanent URI when it is created. Using peer-to-peer |
a permanent URI when it is created. Using peer-to-peer |
26 |
technology, we can find documents even though our URIs |
technology, we can locate documents even though our URIs |
27 |
do not include location information. |
do not include location information. |
28 |
Thus, links continue to work unchanged when documents are emailed |
Thus, links continue to work unchanged when documents are emailed |
29 |
or published on the network. |
or published on the network. |
30 |
|
|
31 |
|
.. Do we really want to talk about NC4 (since it's rather old) ?-) |
32 |
|
OTOH, mentioning KDE is good as it's a "desktop enviroment" (not |
33 |
|
just a single "program") [HH] |
34 |
|
|
35 |
We have extended KDE and Netscape Communicator 4 to understand |
We have extended KDE and Netscape Communicator 4 to understand |
36 |
our experimental URIs. Most other systems can use Storm |
our experimental URIs. Most other systems can use Storm |
37 |
through an HTTP gateway. |
through an HTTP gateway. |
72 |
on the desktop is broken links. A user receiving |
on the desktop is broken links. A user receiving |
73 |
hyperlinked documents by email, for example, would have to reconstruct |
hyperlinked documents by email, for example, would have to reconstruct |
74 |
the original directory structure; otherwise the links |
the original directory structure; otherwise the links |
75 |
won't work. |
will not work. |
76 |
|
|
77 |
|
.. Include to the paragraph above ? |
78 |
|
"A major reason is that links break when documents are moved |
79 |
|
around or sent by mail." [HH] |
80 |
|
|
81 |
.. using location-independent identifiers for |
.. using location-independent identifiers for |
82 |
non-breaking links: |
non-breaking links: |
83 |
|
|
84 |
If desktop documents could be refered to independently |
If desktop documents could be refered to independently |
85 |
of their location, it would be possible to make |
of their location, it would be feasible to make |
86 |
non-breaking links to them. When a document is published |
non-breaking links to them: When a document is published |
87 |
on the Web, it would have the same URI as on the |
on the Web, it would have the same URI as on the |
88 |
author's desktop. When a link to a document is emailed, |
author's desktop; when a link to a document is emailed, |
89 |
the receiver could follow the link as long as their |
the receiver could follow the link as long as their |
90 |
computer can find the linked document-- on its local |
software can locate the linked document-- on its local |
91 |
harddisk, attached to another email, or on the |
harddisk, attached to another email, or on the |
92 |
public Internet. |
public Internet. |
93 |
|
|
94 |
.. Freenet's cryptographical identifiers: |
.. Freenet's cryptographical identifiers: |
95 |
|
|
96 |
Location-independent identifiers aren't a new idea. |
Location-independent identifiers are not a new idea. |
97 |
In Freenet [freenet-ieee]_, an anonymous peer-to-peer |
In Freenet [freenet-ieee]_, an anonymous peer-to-peer |
98 |
publication system, *cryptographic hashes* [bakhtiari95cryptographic]_ |
publication system, *cryptographic hashes* [bakhtiari95cryptographic]_ |
99 |
are used to identify versions of documents. Hashes |
are used to identify versions of documents. Hashes |
127 |
rendered this assumption obsolete. Distributed hashtables (DHTs) |
rendered this assumption obsolete. Distributed hashtables (DHTs) |
128 |
[malkhi02viceroy-andalso-maymounkov02kademlia-andalso-ratnasamy01can-andalso-stoica01chord-andalso-zhao01tapestry]_ |
[malkhi02viceroy-andalso-maymounkov02kademlia-andalso-ratnasamy01can-andalso-stoica01chord-andalso-zhao01tapestry]_ |
129 |
allow location-independent identifiers |
allow location-independent identifiers |
130 |
to be resolved on a global scale. |
to be resolved on a global scale. In fact, authors argue in |
131 |
|
[balakrishnan03semanticfree]_ that DHTs are suitable for the next generation |
132 |
|
Reference Resolutions Services (RRS) [#]_. |
133 |
|
|
134 |
|
.. [#] Domain Name System (DNS) [rfc1101]_ is a widely used RRS |
135 |
|
system in the Internet. |
136 |
|
|
137 |
.. can be used to implement external links, backlinks &c: |
.. can be used to implement external links, backlinks &c: |
138 |
|
|
177 |
|
|
178 |
Browsers and applications can access Storm either |
Browsers and applications can access Storm either |
179 |
by using the Java library directly or through an |
by using the Java library directly or through an |
180 |
HTTP gateway, which, given a Storm URN, finds and |
HTTP gateway, which locates and |
181 |
returns the associated file. Documents can be |
returns the associated file when a Storm URN is given. |
182 |
uploaded into Storm through the gateway, using HTTP PUT. |
Documents can be uploaded into Storm through the gateway, |
183 |
|
using HTTP PUT. |
184 |
|
|
185 |
.. Applications we are integrated with: |
.. Applications we are integrated with: |
186 |
|
|
194 |
.. OpenOffice can load from http gateway |
.. OpenOffice can load from http gateway |
195 |
(needs more complete WebDAV impl to save): |
(needs more complete WebDAV impl to save): |
196 |
|
|
197 |
The Emacs text editor doesn't understand Storm |
The Emacs text editor does not understand Storm |
198 |
URNs yet, but can load and save documents in |
URNs yet, but can load and save documents in |
199 |
Storm using the HTTP gateway. OpenOffice.org |
Storm using the HTTP gateway. OpenOffice.org software |
200 |
can load documents through the HTTP gateway, |
can load documents through the HTTP gateway, |
201 |
but cannot save changes, because the gateway |
but cannot save changes, since the gateway |
202 |
does not yet support WebDAV (HTTP-based distributed |
does not yet support WebDAV (HTTP-based distributed |
203 |
authoring and versioning). |
authoring and versioning). |
204 |
|
|
224 |
This may help in making hyperlinks between desktop |
This may help in making hyperlinks between desktop |
225 |
documents more convenient. |
documents more convenient. |
226 |
|
|
227 |
A distributed hashtable is used to find published documents. |
A distributed hashtable is used to locate published documents. |
228 |
While the core of Storm has been in use for almost |
While the core of Storm has been in use for almost |
229 |
three years, the peer-to-peer subsystem has only recently |
three years, the peer-to-peer subsystem has only recently |
230 |
been implemented. |
been implemented. |