86 |
and connecting to each other directly. Additionally, the distributed and ad hoc nature of |
and connecting to each other directly. Additionally, the distributed and ad hoc nature of |
87 |
Peer-to-Peer improves scalability and avoids single points of failure. |
Peer-to-Peer improves scalability and avoids single points of failure. |
88 |
|
|
89 |
There are many definitions of Peer-to-Peer networks. The Intel Peer-to-Peer |
There are many definitions of Peer-to-Peer networks. Schollmeier \cite{schollmeier01p2pdefinition} |
90 |
Working Group defines it as ''the sharing of computer resources and services |
describes a Peer-to-Peer system as a system of |
|
by direct exchange between systems'' \cite{p2pworkinggroup}. |
|
|
Dave Winer \cite{winer00whatisp2p} describes Peer-to-Peer systems as |
|
|
''The user's machine is a client and a server''. |
|
|
Schollmeier \cite{schollmeier01p2pdefinition} characterizes a Peer-to-Peer system as a system of |
|
91 |
distributed entities that share their own services. Thus, Peer-to-Peer systems can be characterized as distributed |
distributed entities that share their own services. Thus, Peer-to-Peer systems can be characterized as distributed |
92 |
systems in which all communication is symmetric and all participants entities have similar |
systems in which all communication is symmetric and all participants entities have similar |
93 |
capabilities and responsibilities. Each entity, i.e., \emph{peer}, may contribute services |
capabilities and responsibilities. Each entity, i.e., \emph{peer}, may contribute services |
100 |
Peer-to-Peer systems and divide problems into three sub-categories: security problems, |
Peer-to-Peer systems and divide problems into three sub-categories: security problems, |
101 |
performance problems and miscellaneous problems. |
performance problems and miscellaneous problems. |
102 |
|
|
103 |
Next, we give an overview of Fenfire project. Fenfire project is an attempt to build hyperstructured, |
We give an overview of Fenfire project. Fenfire project is an attempt to build hyperstructured, |
104 |
seamlessly interoperating desktop environment. Additional features of Fenfire include innovative user |
seamlessly interoperating desktop environment. Additional features of Fenfire include innovative user |
105 |
interfaces for viewing data and usage of Peer-to-Peer networking for network transparency. In Fenfire, |
interfaces for viewing data and usage of Peer-to-Peer networking for network transparency. In Fenfire, |
106 |
all data is stored in the same format, i.e., data blocks. All blocks have globally unique |
all data is stored in the same format, i.e., data blocks. All blocks have globally unique |
793 |
\parbox{37pt}{$O(1)$} & |
\parbox{37pt}{$O(1)$} & |
794 |
\parbox{37pt}{$O(1)$} & |
\parbox{37pt}{$O(1)$} & |
795 |
\parbox{37pt}{$O(n)$} & |
\parbox{37pt}{$O(n)$} & |
796 |
\parbox{85pt}{Can be 1-10000 connections (aka social connections, connections are permanent)} & |
\parbox{85pt}{Can be 1-10000 connections (as known as ''social'' connections, connections are permanent)} & |
797 |
\parbox{85pt}{Number of connections number depends on peer's memory/network capabilities} |
\parbox{85pt}{Number of connections number depends on peer's memory/network capabilities} |
798 |
\\ \hline |
\\ \hline |
799 |
|
|
1187 |
structured system, peers join and leave the system constantly without any restrictions. On the |
structured system, peers join and leave the system constantly without any restrictions. On the |
1188 |
other hand, however, peers in tightly structured system have less freedom, i.e. overlay chooses peer's |
other hand, however, peers in tightly structured system have less freedom, i.e. overlay chooses peer's |
1189 |
neighbors on behalf of peer itself and maps data items randomly throughout the overlay network. However, |
neighbors on behalf of peer itself and maps data items randomly throughout the overlay network. However, |
1190 |
Peer-to-Peer system is \emph{never} in ''ideal'' state as it is continuouslys evolving system. |
Peer-to-Peer system is \emph{never} in ''ideal'' state as it is continiously evolving system. |
1191 |
|
|
1192 |
Current research has been focused on system management of tightly structured systems, and all presented |
Current research has been focused on system management of tightly structured systems, and all presented |
1193 |
algorithms of tightly structured approach have been analyzed under static simulation environments. Furthermore, proposed |
algorithms of tightly structured approach have been analyzed under static simulation environments. Furthermore, proposed |