128 |
.. XXX Mention "Name-based not possible as a suitable system |
.. XXX Mention "Name-based not possible as a suitable system |
129 |
for names doesn't exist?" |
for names doesn't exist?" |
130 |
|
|
131 |
There are some non-filesharing P2P systems |
We hold that to succeed, a P2P Web would need to provide |
132 |
that do offer an update mechanism. However, none of these |
the following features for users: |
|
provides all the benefits of a filesharing system: |
|
133 |
|
|
134 |
- Being able to download version(s) and use off-line |
Off-line capability |
135 |
- Being able to use neighbour's computer's cache |
The ability to |
136 |
if your LAN is disconnected |
download version(s) and use them off-line without |
137 |
- Being able to keep version online for as long as you want |
a change in the user interface or functionality, |
138 |
- Being able to use different networks: a) withstand |
and to use a neighbouring computer's cache |
139 |
exploit of single network; b) one size doesn't fit all |
if the LAN is disconnected from the internet |
140 |
(e.g. anonymity, efficiency); c) more people can use this |
Heterogeneity |
141 |
(network effect) |
The possibility to |
142 |
|
use different P2P networks interchangeably |
143 |
|
to |
144 |
|
a) withstand |
145 |
|
exploits of single network; b) one size doesn't fit all |
146 |
|
(e.g. anonymity, efficiency); c) more people can use this |
147 |
|
(network effect) |
148 |
|
Distributed archivability |
149 |
|
The ability to |
150 |
|
keep a version originally published by |
151 |
|
someone else online, *accessible to others*, |
152 |
|
for any period of time |
153 |
|
|
154 |
.. To keep a version |
.. To keep a version |
155 |
of a page online, it does not suffice for one user |
of a page online, it does not suffice for one user |
167 |
and stops publishing a page, it disappears, even if |
and stops publishing a page, it disappears, even if |
168 |
someone else has kept a copy. |
someone else has kept a copy. |
169 |
|
|
170 |
|
There are some non-filesharing P2P systems |
171 |
|
that do offer an update mechanism. However, none of these |
172 |
|
provides all the above benefits of a filesharing system: |
173 |
|
|
174 |
... |
... |
175 |
|
|
176 |
Permanence is an important concern, as seen by the following example. |
Permanence is an important concern, as seen by the following example. |
259 |
============ |
============ |
260 |
|
|
261 |
In this section, we shall briefly discuss the existing approaches |
In this section, we shall briefly discuss the existing approaches |
262 |
to document updates in P2P systems. |
to versioning in P2P systems. |
263 |
|
|
264 |
A trivial approach to P2P versioning |
A trivial approach to P2P versioning |
265 |
is to have a centralized server keep track of the current version |
is to have a centralized server keep track of the current version |