7 |
|
|
8 |
.. XXX Abstract is too long ;) |
.. XXX Abstract is too long ;) |
9 |
|
|
10 |
.. XXX Decide on spelling Web page / web page / webpage |
.. XXX Decide on spelling web page / webpage |
11 |
OED says the second one; I'd prefer the third; |
OED says the first; Tuomas would prefer the second. |
|
there are several instances of the first here... |
|
12 |
|
|
13 |
Abstract |
Abstract |
14 |
======== |
======== |
44 |
|
|
45 |
|
|
46 |
.. This loses a major benefit of filesharing: |
.. This loses a major benefit of filesharing: |
47 |
To keep a version of a Web page available, |
To keep a version of a web page available, |
48 |
it should suffice to keep a copy of it on your computer. |
it should suffice to keep a copy of it on your computer. |
49 |
|
|
50 |
.. Instead of being handled specially by a P2P network, |
.. Instead of being handled specially by a P2P network, |
72 |
benefits from hash-based addressing)--- |
benefits from hash-based addressing)--- |
73 |
|
|
74 |
If the Web worked like a filesharing system, there would be |
If the Web worked like a filesharing system, there would be |
75 |
no central point of failure for a Web page; it could be downloaded |
no central point of failure for a web page; it could be downloaded |
76 |
from any host that has a copy. This would save bandwidth |
from any host that has a copy. This would save bandwidth |
77 |
and increase availability. However, if the Web worked like |
and increase availability. However, if the Web worked like |
78 |
a filesharing system, Web pages could not be updated. |
a filesharing system, web pages could not be updated. |
79 |
Some filesharing systems offer permanent URIs for files |
Some filesharing systems offer permanent URIs for files |
80 |
(e.g., [freenet-ieee-andalso-edonkey2kurl]_), |
(e.g., [freenet-ieee-andalso-edonkey2kurl]_), |
81 |
based on the files' cryptographic hashes, |
based on the files' cryptographic hashes, |
82 |
which could be used for linking; but |
which could be used for linking; but |
83 |
a new version of a Web page would have a different hash, |
a new version of a web page would have a different hash, |
84 |
and thus a different URI. [#update]_ |
and thus a different URI. [#update]_ |
85 |
|
|
86 |
.. [#update] When updating a page, it would be clearly |
.. [#update] When updating a page, it would be clearly |
448 |
.. XXX heterogeneous *how*? |
.. XXX heterogeneous *how*? |
449 |
|
|
450 |
Using pointer records, we can provide the functionality |
Using pointer records, we can provide the functionality |
451 |
of static Web pages. While dynamic Web pages generated |
of static web pages. While dynamic web pages generated |
452 |
through server-side scripting and database connections |
through server-side scripting and database connections |
453 |
are certainly important, this still makes up for |
are certainly important, this still makes up for |
454 |
a significant portion of today's Web. |
a significant portion of today's Web. |
551 |
created by pointer records. |
created by pointer records. |
552 |
Through a simple reverse index, it was also easy to implement |
Through a simple reverse index, it was also easy to implement |
553 |
a "backlinks" functionality, which tells the user which |
a "backlinks" functionality, which tells the user which |
554 |
pages link *to* a given Web page. |
pages link *to* a given web page. |
555 |
When run on the local machine, |
When run on the local machine, |
556 |
documents owned by the machine's owner can also be |
documents owned by the machine's owner can also be |
557 |
edited through simple WebDAV clients. |
edited through simple WebDAV clients. |