/[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.106 by benja, Mon Nov 3 23:44:06 2003 UTC revision 1.107 by benja, Mon Nov 3 23:59:14 2003 UTC
# Line 379  is the implementation of a file-shared w Line 379  is the implementation of a file-shared w
379  in a distributed, decentralized and above all  in a distributed, decentralized and above all
380  *heterogeneous* way.  *heterogeneous* way.
381    
382    .. XXX heterogeneous *how*?
383    
384  - standardizing on pointer records such as ours,  Using pointer records, we can provide the functionality
385    can provide full static-page (no CGI, no servlet)  of static Web pages. While dynamic Web pages generated
386    www features set on P2P or just about any type of system  through server-side scripting and database connections
387    are certainly important, this still makes up for
388      - independent of underlying system, each client can use  a significant portion of today's Web.
389        best methods to retrieve page. Analogous to the common HTTP  (We may provide tools for handling simple cases
390        protocol: a language all types of servers and clients  such as showing a list of the newest articles on a news site
391        can speak.  through client-side scripting.)
392    
393          - can have normal filesharing (user decides)  The data model used in this P2P Web is independent
394            but also oceanstore or  from the underlying mechanism used to find data;
395            freenet-like semantics which store data decided  a client could utilize e.g. different overlay networks
396            on by the overlay  with different properties (such as speed and anonymity),
397    the caches of other machines on the LAN,
398      - with ad hoc wireless local networks between mobile devices,  and the complete set of files ever downloaded to the local harddisk.
399        getting e.g. the latest slashdot could be cheaper,  This model is analogous to the HTTP protocol: a common language
400        as the neighbours' caches could be used; trust would not  spoken by all clients and servers.
401        be an issue due to the digital signatures.  
402    In an ad-hoc wireless local network between mobile devices,
403  - need to use opaque pointer ids as addresses;  the latest issue of e.g. Slashdot (an popular online news site)
404    arguments for and against these are discussed in  could be downloaded from other devices' caches, instead
405    [balakrishnan03semanticfree]_  of paying for wireless Internet access; trust would not be
406    an issue as the pointer blocks' signatures could be validated.
407      - should be possible to attach metadata to pointers  
408    The peer-to-peer network we propose would use
409    random-looking, semantic-free identifiers; arguments for this
410    are discussed in [balakrishnan03semanticfree]_.
411    
412  **A distributed wayback machine.**  **A distributed wayback machine.**
413  A surprising benefit of pointer records is that  A surprising benefit of pointer records is that

Legend:
Removed from v.1.106  
changed lines
  Added in v.1.107

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