59 |
and thus a different URI. |
and thus a different URI. |
60 |
|
|
61 |
There are a few (non-file-sharing) P2P systems |
There are a few (non-file-sharing) P2P systems |
62 |
that do offer an update mechanism. *CFS* [XXXref] |
that do offer an update mechanism. *CFS* [dabek01widearea]_ |
63 |
is a file system based on Chord [XXXref], storing |
is a file system based on Chord [stoica01chord]_, storing |
64 |
data in a distributed hashtable (DHT). CFS identifies |
data in a distributed hashtable (DHT). CFS identifies |
65 |
different users' trees by the users' cryptographic keys; |
different users' trees by the users' cryptographic keys; |
66 |
it stores in its DHT mappings from these keys to the |
it stores in its DHT mappings from these keys to the |
69 |
is signed with the appropriate key, and contains a timestamp |
is signed with the appropriate key, and contains a timestamp |
70 |
newer than that of the current version. |
newer than that of the current version. |
71 |
|
|
72 |
In *Oceanstore* [XXXref], every document has a |
In *Oceanstore* [kubiatowicz00oceanstore]_, every document has a |
73 |
*primary replica*, a small set of servers that |
*primary replica*, a small set of servers that |
74 |
maintain the current version of the document. |
maintain the current version of the document. |
75 |
To make the connection between document and version, |
To make the connection between document and version, |
86 |
allowing previous versions of documents to be accessed |
allowing previous versions of documents to be accessed |
87 |
(by using their old heartbeats). |
(by using their old heartbeats). |
88 |
|
|
89 |
*Freenet* [XXXref] was originally planned to have an |
*Freenet* [freenet-ieee]_ was originally planned to have an |
90 |
update mechanism where the network would remember |
update mechanism where the network would remember |
91 |
the current version of a document, and update this information |
the current version of a document, and update this information |
92 |
when receiving a message signed by the appropriate key, |
when receiving a message signed by the appropriate key, |
93 |
rather like in Oceanstore [XXXref]. However, in practice, |
rather like in Oceanstore. However, in practice, |
94 |
Freenet has a rather peculiar combination |
Freenet has a rather peculiar combination |
95 |
of two workarounds [XXXref Freenet FAQ]: |
of two workarounds [freenetfaq]_: |
96 |
|
|
97 |
In date-based updating, the URI for the current version |
In date-based updating, the URI for the current version |
98 |
is formed by concatenating a document's id with the current date; |
is formed by concatenating a document's id with the current date; |
109 |
Finally, a simplistic approach to P2P versioning |
Finally, a simplistic approach to P2P versioning |
110 |
is to have a centralized server keep track of the current version |
is to have a centralized server keep track of the current version |
111 |
of a document, such as in the *Content-Addressable Web* |
of a document, such as in the *Content-Addressable Web* |
112 |
proposal [XXXref -> google it], in which clients download |
proposal [content-addressable-web]_, in which clients download |
113 |
a file's hash through HTTP (using an HTTP URI), |
a file's hash through HTTP (using an HTTP URI), |
114 |
then download the file through, e.g., a file-sharing network. |
then download the file through, e.g., a file-sharing network. |
115 |
This provides some of the efficiency advantages of a P2P Web. |
This provides some of the efficiency advantages of a P2P Web. |
195 |
would have the benefits of semantic-free referencing-- |
would have the benefits of semantic-free referencing-- |
196 |
URIs don't have to change because of trademark conflicts |
URIs don't have to change because of trademark conflicts |
197 |
as in DNS, for example-- but go beyond the proposal |
as in DNS, for example-- but go beyond the proposal |
198 |
by Balakrishnan et.al. [XXXref], which would only |
by Balakrishnan et.al. [balakrishnan03semanticfree]_, which would only |
199 |
replace DNS, but keep the centralized architecture of |
replace DNS, but keep the centralized architecture of |
200 |
one Web server (or a single set of servers) maintained |
one Web server (or a single set of servers) maintained |
201 |
by the publisher of a document. |
by the publisher of a document. |