46 |
and increase availability. However, if the Web worked like |
and increase availability. However, if the Web worked like |
47 |
a file-sharing system, Web pages could never be updated. |
a file-sharing system, Web pages could never be updated. |
48 |
|
|
49 |
|
In this paper, we present a versioning system usable |
50 |
|
for a P2P Web as well as for updateable media files |
51 |
|
in a file-sharing application (e.g. corrected versions |
52 |
|
of Project Gutenberg books) and P2P-based software distribution |
53 |
|
(akin to Debian's ``apt-get`` system). |
54 |
|
|
55 |
Most current P2P systems have no facility |
Most current P2P systems have no facility |
56 |
for updating documents. The systems that do |
for updating documents. The systems that do |
57 |
(such as Freenet or OceanStore) require state in the network |
(such as Freenet or OceanStore) require state in the network |
71 |
This way, versions of a document |
This way, versions of a document |
72 |
stay available as long as anybody keeps a copy. |
stay available as long as anybody keeps a copy. |
73 |
|
|
74 |
|
We also present an elegant and efficient system that |
75 |
|
keeps a full version history while storing only the |
76 |
|
differences between versions. |
77 |
|
|
78 |
.. raw:: latex |
.. raw:: latex |
79 |
|
|
80 |
\endabstract |
\endabstract |