20 |
.. History of location-dependence: `TBL ref`_ (like in HT'03 paper) |
.. History of location-dependence: `TBL ref`_ (like in HT'03 paper) |
21 |
|
|
22 |
.. Location-independent, semantic-free, *self-verifying* |
.. Location-independent, semantic-free, *self-verifying* |
23 |
identifiers (ref SFR paper (Balakrishnan et.al. IPTPS'03), |
identifiers (ref SFR paper [balakrishnan03semanticfree]_, |
24 |
ref Walfish paper); example: hash-based (ref |
[walfish03dns]_); example: hash-based (ref |
25 |
``hash`` URN namespace Internet-Draft; ref Freenet & others) |
``hash`` URN namespace Internet-Draft; ref Freenet & others) |
26 |
|
|
27 |
.. Proposal: A location-independent Web (closest thing is Freenet (ref)) |
.. Proposal: A location-independent Web (closest thing is Freenet (ref)) |
42 |
(storage systems: CFS, PAST; web caching: Squirrel), |
(storage systems: CFS, PAST; web caching: Squirrel), |
43 |
but don't address the Web. |
but don't address the Web. |
44 |
|
|
45 |
|
.. The infrastructure behind CFS, PAST and Squirrel: Peer-to-Peer |
46 |
|
|
47 |
|
.. Quite recently, several Peer-to-Peer architectures have been |
48 |
|
proposed that use hash-based, loc.ind. ids |
49 |
|
|
50 |
.. Possibility of desktop integration in ways that the location-dependent |
.. Possibility of desktop integration in ways that the location-dependent |
51 |
Web cannot archieve, through the unique combination of |
Web cannot archieve, through the novel combination of |
52 |
network transparency and location independence (ref ourselves). |
network transparency and location independence (ref ourselves). |
53 |
|
|
54 |
.. However, there's a problem with this: versioning ----- |
.. However, there's a problem with this: versioning ----- |
68 |
============ |
============ |
69 |
|
|
70 |
- In this section, we summarize how existing |
- In this section, we summarize how existing |
71 |
peer-to-peer systems deal with versioning. |
peer-to-peer systems deal with versioning that use |
72 |
|
hash-based ids. |
73 |
|
|
74 |
|
|
75 |
- No updates: |
- No updates: |
76 |
|
|
77 |
- PAST |
- PAST [rowstron01storage]_ |
78 |
- Free Haven |
- Free Haven [dingledine00free]_ |
79 |
|
|
80 |
- Centralized updates: |
- Centralized updates: |
81 |
|
|
85 |
|
|
86 |
- Network-level destructive updates: |
- Network-level destructive updates: |
87 |
|
|
88 |
- Freenet |
- Freenet [freenet-ieee]_ |
89 |
- SFR (apparently) |
- SFR (apparently) |
90 |
- CFS |
- CFS [dabek01widearea]_ |
91 |
|
|
92 |
- Conclusion: Doesn't provide the benefits of |
- Conclusion: Doesn't provide the benefits of |
93 |
hash-based addressing; doesn't allow accessing |
hash-based addressing; doesn't allow accessing |
99 |
|
|
100 |
- Basic model of underlying system: Only blocks |
- Basic model of underlying system: Only blocks |
101 |
- Benefits of that, in a nutshell |
- Benefits of that, in a nutshell |
102 |
- Reverse indexing (nicely provided through DHT) |
- Reverse indexing (nicely provided through DHT), *define* reverse indexing |
103 |
- Def.: Pointers are abstract references that *point* |
- Def.: Pointers are abstract references that *point* |
104 |
to different blocks (versions) over time |
to different blocks (versions) over time |
105 |
- Storm is designed to be modular; different routing algorithms |
- Storm is designed to be modular; different routing algorithms |
178 |
|
|
179 |
|
|
180 |
.. _TBL ref: http://www.w3.org/DesignIssues/NameMyth.html#What |
.. _TBL ref: http://www.w3.org/DesignIssues/NameMyth.html#What |
181 |
|
|
182 |
|
.. bibliography:: ../gzigzag |