13 |
Abstract |
Abstract |
14 |
======== |
======== |
15 |
|
|
16 |
|
- The Web should keep previous versions as long as someone |
17 |
|
is interested, even if the original publisher has lost interest |
18 |
|
- File sharing systems kind of do that |
19 |
|
- But you can't update files in them |
20 |
|
- P2P systems that do support updating don't support |
21 |
|
this notion of permanence |
22 |
|
- We present a simple model that *does* do it |
23 |
|
- We present an even simpler model that it could be |
24 |
|
implemented upon; the simpler model maps directly |
25 |
|
to many current p2p systems |
26 |
|
- It can thus use different P2P networks as backends, |
27 |
|
and could thus become a agreed-upon way to do |
28 |
|
versioning (we believe that the current systems, |
29 |
|
which require state to be kept in *one* of the networks |
30 |
|
really can not) |
31 |
|
|
32 |
The Web could benefit greatly from the bandwith savings, |
The Web could benefit greatly from the bandwith savings, |
33 |
increased availability, and reduced server costs offered |
increased availability, and reduced server costs offered |
34 |
by filesharing systems. |
by filesharing systems. |