/[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.127 by tjl, Wed Nov 5 12:35:04 2003 UTC revision 1.128 by benja, Wed Nov 5 14:56:43 2003 UTC
# Line 37  data model, several P2P networks can be Line 37  data model, several P2P networks can be
37  as a P2P Web (except, naturally, for dynamically generated CGI pages),  as a P2P Web (except, naturally, for dynamically generated CGI pages),
38  and  and
39  web pages  web pages
40  can reside on any host, even moved to computers  can reside on any host, even moved
41  that are off-line through physical media or archived,  through physical media
42    to computers
43    that are off-line,
44  without having to change the reference.  without having to change the reference.
45  Past versions of a web page  Past versions of a web page
46  remain accessible as long as anybody keeps a copy.  remain accessible as long as anybody keeps a copy.
47  We discuss our preliminary implementation,  We discuss our preliminary implementation,
48  and  and
49  applications to  applications of pointer records and the Storm data model to
50  P2P-based software distribution and upgrading,  P2P-based software distribution and upgrading,
51    
52    
# Line 80  If the Web worked like a filesharing sys Line 82  If the Web worked like a filesharing sys
82  no central point of failure for a Web page; it could be downloaded  no central point of failure for a Web page; it could be downloaded
83  from any host that has a copy. This would save bandwidth  from any host that has a copy. This would save bandwidth
84  and increase availability. However, if the Web worked like  and increase availability. However, if the Web worked like
85  a filesharing system, Web pages could not be updated easily.  a filesharing system, Web pages could not be updated.
86  Some filesharing systems offer permanent URIs for files  Some filesharing systems offer permanent URIs for files
87  (e.g., [freenet-ieee-andalso-edonkey2kurl]_),  (e.g., [freenet-ieee-andalso-edonkey2kurl]_),
88  based on the files' cryptographic hashes.  based on the files' cryptographic hashes,
89  A new version of a Web page would have a different hash,  which could be used for linking; but
90  and thus a different URI. Others could be confused by  a new version of a Web page would have a different hash,
91  finding two files with the same name but different content (XXX).  and thus a different URI. [#update]_
92    
93    .. [#update] When updating a page, it would be clearly
94       infeasible to update all pages linking to it, and thus
95       all pages linking to *them*, and thus...
96    
97  There are some (non-filesharing) P2P systems  There are some (non-filesharing) P2P systems
98  that do offer an update mechanism. *CFS* [dabek01widearea]_  that do offer an update mechanism. *CFS* [dabek01widearea]_

Legend:
Removed from v.1.127  
changed lines
  Added in v.1.128

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