/[gzz]/manuscripts/pointers/article.rst
ViewVC logotype

Diff of /manuscripts/pointers/article.rst

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.122 by tjl, Tue Nov 4 10:03:27 2003 UTC revision 1.123 by tjl, Tue Nov 4 10:24:04 2003 UTC
# Line 172  Almost two thirds of the debate Line 172  Almost two thirds of the debate
172  has fallen off the Web. "If I have seen further it is by standing  has fallen off the Web. "If I have seen further it is by standing
173  on the shoulders of giants;" but how can we do that today,  on the shoulders of giants;" but how can we do that today,
174  if the shoulders keep rotting away?  if the shoulders keep rotting away?
175    The Internet Archive's Wayback Machine [waybackmachine]_
176    alleviates these concerns somewhat, but it introduces
177    a single point of failure-- and censorship-- for the *entire* Web!
178    
179  .. [#rtg-links] ``http://www.seds.org/spaceviews/cassini/ rtgpages.html``.  .. [#rtg-links] ``http://www.seds.org/spaceviews/cassini/ rtgpages.html``.
180     All links dereferenced on October 27th, 2003.     All links dereferenced on October 27th, 2003.
181    
 (The Internet Archive's Wayback Machine [waybackmachine]_  
 alleviates these concerns, but it introduces  
 a single point of failure-- and censorship-- for the *entire* Web!)  
   
182  .. <<<We don't propose that every byte of information ever published  .. <<<We don't propose that every byte of information ever published
183     on the Web has to be kept around forever. However,     on the Web has to be kept around forever. However,
184     we do believe that as long as someone does keep a copy,     we do believe that as long as someone does keep a copy,
# Line 194  a single point of failure-- and censorsh Line 193  a single point of failure-- and censorsh
193     Web cannot archieve, through the novel combination of     Web cannot archieve, through the novel combination of
194     network transparency and location independence (ref ourselves).     network transparency and location independence (ref ourselves).
195    
196  The main contribution of our paper are *pointer records*,  The main contribution of this paper is the use of *pointer records*,
197  a versioning mechanism which is similar to OceanStore's heartbeats,  a versioning mechanism which is similar to OceanStore's heartbeats,
198  but makes the clients download and store the pointer records  but allows the clients to download and store the pointer records
199  along with the corresponding version of a document.  along with the corresponding version of a document.
200  If a client saves a version of a document locally, it  If a client caches a version of a document locally, it
201  stores the pointer record along with it. Thus, in our system,  stores the pointer record along with it.
 a version of a document truly remains accessible as long as  
 anybody keeps a copy of it.  
   
202  Instead of having a primary replica, we search  Instead of having a primary replica, we search
203  a P2P network for current pointer records  the P2P network for current pointer records
204  related to a document; we pick the one with  related to a document; we pick the one with
205  the most current timestamp as the version  the most current timestamp as the version
206  to show to the user. Like in OceanStore, old  to show to the user by default; old versions
207  versions remain fully accessible (as long as somebody  remain equally accessible
208  keeps a copy).  as long as
209    anybody keeps a copy.
210    
211    ..  Like in OceanStore, old
212        versions remain fully accessible (as long as somebody
213        keeps a copy).
214    
215  We propose to use pointer records along with hash-based  We propose to use pointer records along with hash-based
216  addressing to implement a P2P-based replacement  addressing to implement a P2P-based replacement
217  for the static Web (not including dynamic pages  for the Web (not including dynamic pages
218  generated through server-side scripting). Such a Web  generated through server-side scripting). Such a Web
219  would have the benefits of semantic-free referencing--  would have the benefits of semantic-free referencing--
220  URIs don't have to change because of trademark conflicts  URIs don't have to change because of trademark conflicts
221  as in DNS, for example-- but go beyond the proposal  as in DNS, for example-- but go beyond the proposal
222  by Balakrishnan et.al. [balakrishnan03semanticfree]_, which would only  by Balakrishnan et.al. [balakrishnan03semanticfree]_,
223  replace DNS, but keep the centralized architecture of  for replacing DNS but keeping the centralized architecture of
224  one Web server (or a single set of servers) maintained  one Web server (or a single set of servers) maintained
225  by the publisher of a document.  by the publisher of a document.
226    
227  The remainder of this paper is structured as follows.  The remainder of this paper is structured as follows.
228  In Section 2, we introduce pointer records.  In Section 2, we introduce pointer records.
229  In Section 3, we propose a simple, hash-based data model  In Section 3, we discuss the minimal hash-based data model required
230  that can be used by P2P Web servers and clients.  for implementing pointers.
231  In Section 4 we discuss other possible applications  In Section 4 we discuss other possible applications
232  of pointer records, and Section 5 gives an overview of our  of pointer records, and Section 5 gives an overview of our
233  implementation. Section 6 concludes.  implementation. Section 6 concludes.

Legend:
Removed from v.1.122  
changed lines
  Added in v.1.123

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26