19 |
%*********************** |
%*********************** |
20 |
\title{Fenfire in Peer-to-Peer Enviroment} |
\title{Fenfire in Peer-to-Peer Enviroment} |
21 |
|
|
22 |
\translatedtitle{Fenfire in Peer-to-Peer Enviroment} |
\translatedtitle{Fenfire vertaisverkko ympäristössä} |
23 |
|
|
24 |
\author{Hermanni Hyytiälä} |
\author{Hermanni Hyytiälä} |
25 |
|
|
27 |
|
|
28 |
\tyyppi{Master's Thesis} |
\tyyppi{Master's Thesis} |
29 |
|
|
30 |
\keywords{Peer-to-Peer, P2P, Hypermedia, Distributed systems} |
\keywords{Peer-to-Peer, P2P, security, Distributed systems} |
31 |
|
|
32 |
\avainsanat{Vertaisverkot, Hypermedia, hajautetut järjestelmät} |
\avainsanat{Vertaisverkot, P2P, tietoturva, hajautetut järjestelmät} |
33 |
|
|
34 |
\contactinformation{\\ |
\contactinformation{\\ |
35 |
Hermanni Hyytiälä\\ |
Hermanni Hyytiälä\\ |
39 |
|
|
40 |
|
|
41 |
\abstract{ |
\abstract{ |
42 |
In this thesis we review existing Peer-to-Peer approaches, protocols and their |
In this thesis, we review existing Peer-to-Peer approaches, protocols and their |
43 |
key properties. We summarize open problems in Peer-to-Peer networks and divide |
key properties. We summarize open problems in Peer-to-Peer networks and divide |
44 |
problems into three sub-categories. We observe that there are many |
problems into three sub-categories. We observe that there are many |
45 |
problems, which have not solutions at all, or problems have proposed |
problems, which have not solutions at all, or problems have proposed |
60 |
|
|
61 |
Tämän jälkeen annamme yleiskuvan Fenfire-järjestelmästämme ja kuvaamme |
Tämän jälkeen annamme yleiskuvan Fenfire-järjestelmästämme ja kuvaamme |
62 |
vertaisverkkotoiminnallisuuden kannalta Fenfiren tärkeimmät ohjelmamoduulit. |
vertaisverkkotoiminnallisuuden kannalta Fenfiren tärkeimmät ohjelmamoduulit. |
63 |
Arvioimme olemassaolevia vertaisverkkoarkkitehtuureja- löyhästi ja tiukasti |
Ar-vioimme olemassaolevia vertaisverkkoarkkitehtuureja- löyhästi ja tiukasti |
64 |
rakennettuja päällysverkkoja- Fenfiren vaatimusten valossa. Lopuksi ehdotamme |
rakennettuja päällysverkkoja- Fenfiren vaatimusten valossa. Lopuksi ehdotamme |
65 |
yksinkertaisia algoritmeja, joiden avulla voidaan tehokkaasti löytää |
yksin-kertaisia algoritmeja, joiden avulla voidaan tehokkaasti löytää |
66 |
vertaisverkosta tietoa Fenfire:n liittyen. |
vertaisverkosta tietoa Fenfire:n liittyen. |
67 |
} |
} |
68 |
|
|
87 |
provides new, direct way to achieve interoperability between network participants. |
provides new, direct way to achieve interoperability between network participants. |
88 |
Finally, the distributed and ad-hoc nature of Peer-to-Peer improves scalability |
Finally, the distributed and ad-hoc nature of Peer-to-Peer improves scalability |
89 |
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). |
90 |
|
|
91 |
There are many definitions of Peer-to-Peer networks. The Intel Peer-to-Peer |
There are many definitions of Peer-to-Peer networks. The Intel Peer-to-Peer |
92 |
Working Group defines is as ''the sharing of computer resources and defines |
Working Group defines is as ''the sharing of computer resources and defines |
93 |
and services by direct exchange between systems''. Dave Winer \cite{winer00whatisp2p} lists several |
and services by direct exchange between systems''. Dave Winer \cite{winer00whatisp2p} lists several |
94 |
properties of Peer-to-Peer network, while most notably the statement |
properties of Peer-to-Peer network, while most notably the statement |
95 |
''The user's machine is a client and a server'' describes best Peer-to-Peer |
''The user's machine is a client and a server'' describes best Peer-to-Peer |
96 |
networks. |
networks. To summarize, Peer-to-Peer systems can be characterized as distributed |
|
|
|
|
To summarize, Peer-to-Peer systems can be characterized as distributed |
|
97 |
systems in which all communication is symmetric and all participants have identical |
systems in which all communication is symmetric and all participants have identical |
98 |
capabilities and responsabilities. Each \emph{peer} may contribute data or |
capabilities and responsabilities. Each \emph{peer} may contribute data or |
99 |
computing resources (e.g., unused storage) to the overall system and the welfare |
computing resources (e.g., unused storage) to the overall system and the welfare |
112 |
problems in easy-to-understand tables. |
problems in easy-to-understand tables. |
113 |
|
|
114 |
Next, we give an overview of our Fenfire system, which implements xanalogical storage model. We |
Next, we give an overview of our Fenfire system, which implements xanalogical storage model. We |
115 |
also describe briefly Storm design and urn-5 concept, which are essential to Fenfire's |
also describe briefly Storm software module, which is essential part of Fenfire's |
116 |
Peer-to-Peer functionality. We evaluate existing Peer-to-Peer approaches and |
Peer-to-Peer functionality. We evaluate existing Peer-to-Peer approaches and |
117 |
choose the best alternative to our needs. We discover that Storm, xanalogical model and |
choose the best alternative to our needs. We discover that Storm, xanalogical model and |
118 |
tightly structured Peer-to-Peer approach all have similar method to deal with data, |
tightly structured Peer-to-Peer approach all have similar method to deal with data, |