71 |
\large |
\large |
72 |
{\bf Why and how ?} |
{\bf Why and how ?} |
73 |
\begin{itemize} |
\begin{itemize} |
74 |
\item Location transparency: hiding the heterogeneous and distributed nature of the system |
\item Location transparency in Fenfire: hiding the heterogeneous and distributed nature of the system |
75 |
so that it appears to the end user like one system |
so that it appears to the end user like one system |
76 |
\item Ad hoc: meet other people, change data |
\item Ad hoc nature in Fenfire: meet other people, change data |
77 |
\item Storm module is used for low level storage operations |
\item Storm module is used for low level storage operations (Storm blocks) |
78 |
\item Alph module is used for xanalogical operations |
\item Alph module is used for xanalogical operations (xanalogical links, transclusions etc.) |
79 |
|
\item Alph is built upon Storm |
80 |
\end{itemize} |
\end{itemize} |
81 |
\end{slide} |
\end{slide} |
82 |
|
|
83 |
|
|
84 |
\begin{slide} |
\begin{slide} |
85 |
\large |
\large |
86 |
{\bf P2P objectives} |
{\bf Objectives} |
87 |
\begin{itemize} |
\begin{itemize} |
88 |
\item Find data from P2P network, i.e., building blocks of xanalogical ''virtual document'' |
\item Find data from P2P network, i.e., building blocks of xanalogical ''virtual document'' |
89 |
\item Find xanalogical links and transclusions from P2P network |
\item Find xanalogical links and transclusions from P2P network |
90 |
\item Scalable (billions of users) |
\item Scalable (billions of users) |
91 |
\item Efficient (logarithmic efficiency) |
\item Efficient (logarithmic efficiency) |
92 |
\item Robust against network failures, fault tolerant against hostile attack |
\item Resilience in adverse conditions: robust against network failures, fault tolerant against hostile attacks |
93 |
\end{itemize} |
\end{itemize} |
94 |
\end{slide} |
\end{slide} |
95 |
|
|
106 |
\item All identifiers are globally unique (pointers and blocks identifiers) |
\item All identifiers are globally unique (pointers and blocks identifiers) |
107 |
\item Identifiers are unstructured and semantic free |
\item Identifiers are unstructured and semantic free |
108 |
\item Used in next generation Reference Resolution Services (RRS) ? [Shenker] |
\item Used in next generation Reference Resolution Services (RRS) ? [Shenker] |
109 |
\item Currently, Domain Name System (DNS) is a widely used RRS system in the Internet |
\item Domain Name System (DNS) is a widely used RRS system in the Internet |
110 |
\end{itemize} |
\end{itemize} |
111 |
\end{slide} |
\end{slide} |
112 |
|
|
115 |
\large |
\large |
116 |
{\bf P2P schemes 1/2} |
{\bf P2P schemes 1/2} |
117 |
\begin{itemize} |
\begin{itemize} |
118 |
\item There are only two approaches in which all modern Peer-to-Peer |
\item There are only two schemes in which all modern Peer-to-Peer |
119 |
systems fall: the loosely structured approach and the tightly structured approach |
systems fall: the loosely structured approach and the tightly structured approach |
120 |
\item Structure: how the connections between participating peers are created |
\item Structure: how the connections between participating peers are created |
121 |
and maintained |
and maintained |