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 |
266 |
of a document, as in the *Content-Addressable Web* |
of a document, as in the *Content-Addressable Web* |
267 |
proposal [content-addressable-web]_, in which clients download |
proposal [content-addressable-web]_. Clients download |
268 |
a file's hash through HTTP (using an HTTP URI), |
a file's hash through HTTP, |
269 |
and can then obtain |
and can then obtain |
270 |
the file through, e.g., a filesharing network. |
the file through, e.g., a filesharing network. |
271 |
This provides some of the efficiency advantages of a P2P Web. |
This provides some of the efficiency advantages of a P2P Web. |