251 |
taken together form a full history of the document. |
taken together form a full history of the document. |
252 |
The list of available records can be obtained through a |
The list of available records can be obtained through a |
253 |
peer-to-peer network; this could be a DHT, a flooding broadcasting |
peer-to-peer network; this could be a DHT, a flooding broadcasting |
254 |
network like Gnutella [gnutellauri]_, or any other P2P architecture. |
network like Gnutella [gnutellaurl]_, or any other P2P architecture. |
255 |
|
|
256 |
In addition to the above information, a pointer record |
In addition to the above information, a pointer record |
257 |
may contain a list of versions that the current version |
may contain a list of versions that the current version |
302 |
Primitive block storage abstraction |
Primitive block storage abstraction |
303 |
=================================== |
=================================== |
304 |
|
|
305 |
In this Section, we shall |
In this section, we introduce a simple data model that |
306 |
discuss the requirements for using pointer blocks |
|
307 |
|
|
308 |
explicitly state the capabilities |
explicitly state the capabilities |
309 |
that our pointer scheme requires from the underlying system. |
that our pointer scheme requires from the underlying system. |