50 |
% Teksti alkaa... |
% Teksti alkaa... |
51 |
%*********************** |
%*********************** |
52 |
|
|
53 |
\section{Introduction} |
\chapter{Introduction} |
54 |
|
|
55 |
Peer-to-Peer (P2P) systems can be characterized as distributed systems in which all |
Peer-to-Peer (P2P) systems can be characterized as distributed systems in which all |
56 |
communication is symmetric and all participants have identical capabilities and responsabilities. |
communication is symmetric and all participants have identical capabilities and responsabilities. |
63 |
of reasons. First, the lack of decentralization means that participants can form a P2P system without any |
of reasons. First, the lack of decentralization means that participants can form a P2P system without any |
64 |
investment to high-priced hardware to coordinate it. Moreover, P2P systems provides aggregation of enormous |
investment to high-priced hardware to coordinate it. Moreover, P2P systems provides aggregation of enormous |
65 |
resources and way to achieve interoperability. Finally, the distributed nature of P2P improves scalability |
resources and way to achieve interoperability. Finally, the distributed nature of P2P improves scalability |
66 |
and reliability againts certain kinds of faults, e.g. single point of failure. |
and reliability againts certain kinds of faults, e.g. single point of failure. |
67 |
|
|
68 |
|
\chapter{Related Work} |
69 |
|
|
70 |
|
|
71 |
\section{Peer-to-Peer Systems} |
\chapter{Overview of P2P} |
72 |
|
|
73 |
This section discusses briefly general aspects of P2P systems. A more detailed general discussion can be found |
This section discusses briefly general aspects of P2P systems. A more detailed general discussion can be found |
74 |
from \cite{milojicic02peertopeer, oram01harnessingpower}. |
from \cite{milojicic02peertopeer, oram01harnessingpower}. |
75 |
|
|
76 |
|
|
77 |
\subsection{What is P2P ?} |
\section{What is P2P ?} |
78 |
|
|
79 |
Altough the exact definition of "peer-to-peer" is debatable, these systems typically lack dedicated, centralized |
Altough the exact definition of "peer-to-peer" is debatable, these systems typically lack dedicated, centralized |
80 |
infrastructure, resources and services depends on the voluntary participation of peers. Because of that, the |
infrastructure, resources and services depends on the voluntary participation of peers. Because of that, the |
123 |
|
|
124 |
|
|
125 |
|
|
126 |
\subsection{A brief history of Peer-to-Peer Systems} |
\section{A brief history of Peer-to-Peer Systems} |
127 |
|
|
128 |
The Internet has been originally established in the late 1960s \cite{oram01harnessingpower}. |
The Internet has been originally established in the late 1960s \cite{oram01harnessingpower}. |
129 |
The aim of the ARPANET-project was to share computers' resources around the |
The aim of the ARPANET-project was to share computers' resources around the |
134 |
Internet [REFERENCE NEEDED!!!]. |
Internet [REFERENCE NEEDED!!!]. |
135 |
|
|
136 |
While most early distributed applications can be considered P2P, e-mail systems and Usenet |
While most early distributed applications can be considered P2P, e-mail systems and Usenet |
137 |
News were probably the most widely used. In both cases, local server created connections to |
News were probably the most extensively used. In both cases, local server created connections to |
138 |
other peer servers to deliver messages into the user's mail box or into a spool box |
other peer servers to deliver messages into the user's mail box or into a spool box |
139 |
containing messages from the newsgroups. The File Transfer Protocol (FTP) can be considered as a |
containing messages from the newsgroups. The File Transfer Protocol (FTP) can be considered as a |
140 |
predecessor to today's file-sharing P2P systems. Eventually, Archie indexing system, was developed to |
predecessor to today's file-sharing P2P systems. Eventually, the Archie indexing system, was developed to |
141 |
provide a central search mechanism over existing FTP servers. Napster \cite{napsterurl} is a good |
provide a central search infrastructure over existing FTP servers. Napster \cite{napsterurl} is a good |
142 |
example of this kind of model in modern P2P file-sharing systems. |
example of this kind of approach in modern P2P file-sharing systems. |
143 |
|
|
144 |
\subsection{Applications} |
\section{Characteristics of P2P} |
145 |
|
|
146 |
\subsection{Security} |
\subsection{Decentralization} |
147 |
|
|
148 |
\subsection{Piracy} |
\subsection{Scalability and Adaption} |
149 |
|
|
150 |
\subsection{Business} |
\subsection{Anonymity and Autonomy} |
151 |
|
|
152 |
|
\subsection{Self-Organization} |
153 |
|
|
154 |
\section{Existing Peer-to-Peer systems} |
\subsection{Cost of Ownership} |
155 |
|
|
156 |
|
\subsection{Ad-Hoc Connectivity} |
157 |
|
|
158 |
|
\section{Types of P2P Systems} |
159 |
|
|
160 |
|
\subsection{Distributed Computing} |
161 |
|
|
162 |
|
\subsection{File and Content Sharing} |
163 |
|
|
164 |
|
\subsection{Colloboration} |
165 |
|
|
166 |
|
\subsection{Platforms} |
167 |
|
|
168 |
|
\chapter{Existing P2P file-sharing systems} |
169 |
|
|
170 |
|
\section{Flooding broadcast systems} |
171 |
|
|
172 |
|
\subsection{Gnutella} |
173 |
|
\subsection{FastTrack} |
174 |
|
\subsection{Gnutella2} |
175 |
|
|
176 |
|
\section{Distributed hash table systems} |
177 |
|
|
178 |
|
\subsection{Plaxton} |
179 |
|
|
180 |
|
\subsection{OceanStore} |
181 |
|
|
182 |
|
\subsection{Tapestry} |
183 |
|
|
184 |
|
\subsection{Pastry} |
185 |
|
|
186 |
|
\subsection{Chord} |
187 |
|
|
188 |
|
\subsection{CAN} |
189 |
|
|
190 |
|
\subsection{GISP} |
191 |
|
|
192 |
|
\subsection{...} |
193 |
|
|
194 |
|
\section{Distributed Sloppy Hash Tables} |
195 |
|
|
196 |
|
\subsection{Coral} |
197 |
|
|
198 |
|
\section{Hybrid systems} |
199 |
|
|
200 |
|
\subsection{Yappers} |
201 |
|
|
202 |
|
\section{Tree based systems} |
203 |
|
|
204 |
|
\subsection{Kademlia} |
205 |
|
|
206 |
|
\section{Selective forwarding systems} |
207 |
|
|
208 |
|
\subsection{Freenet} |
209 |
|
|
210 |
|
\section{Social Discovery Mechanism} |
211 |
|
|
212 |
|
\subsection{Alpine} |
213 |
|
|
214 |
|
\section{Future} |
215 |
|
|
216 |
|
\chapter{Open Problems in P2P Systems} |
217 |
|
|
218 |
|
\section{Scalability} |
219 |
|
|
220 |
|
\section{Resource Discovery} |
221 |
|
|
222 |
|
\section{Routing Algorithms for DHT} |
223 |
|
|
224 |
|
\section{Complex Queries in DHT systems} |
225 |
|
|
226 |
|
\section{Dynamic Data Placement Problem} |
227 |
|
|
228 |
|
\section{Security} |
229 |
|
|
230 |
|
\subsection{File Authenticy} |
231 |
|
|
232 |
|
\subsection{Access Control} |
233 |
|
|
234 |
|
\subsection{Availability} |
235 |
|
|
236 |
|
\subsection{Anonymity} |
237 |
|
|
238 |
|
|
239 |
|
\chapter{Overview of Gzz system} |
240 |
|
|
241 |
|
\section{Overview of Gzz} |
242 |
|
|
243 |
|
\section{Xanalogical model} |
244 |
|
|
245 |
|
\section{ZigZag hyperstructure} |
246 |
|
|
247 |
|
\section{Storm} |
248 |
|
|
249 |
|
\chapter{Gzz and P2P} |
250 |
|
|
251 |
|
\section{Motivation} |
252 |
|
|
253 |
|
\section{Special Requirements} |
254 |
|
|
255 |
|
\section{Benefits} |
256 |
|
|
257 |
|
\chapter{Conclusion} |
258 |
|
|
|
\subsection{Search Methods} |
|
259 |
|
|
260 |
- - - - |
- - - - |
261 |
|
|
789 |
resource discovery in large peer based networks can be implemented successfully. |
resource discovery in large peer based networks can be implemented successfully. |
790 |
|
|
791 |
|
|
792 |
|
\bibliographystyle{gradu} |
|
\subsection{Business} |
|
|
\subsection{Business} |
|
|
\subsection{Business} |
|
|
\subsection{Business} |
|
|
\subsection{Business} |
|
|
\subsection{Business} |
|
|
|
|
|
|
|
|
\section{Gzz system} |
|
|
|
|
|
\section{Gzz and Peer-to-Peer network} |
|
|
|
|
|
\section{Conclusion} |
|
|
\bibliographystyle{plain} |
|
793 |
\bibliography{progradu} |
\bibliography{progradu} |
794 |
|
|
795 |
|
|