1788 |
\section{Evaluation of Peer-to-Peer approaches with regard to Fenfire} |
\section{Evaluation of Peer-to-Peer approaches with regard to Fenfire} |
1789 |
|
|
1790 |
In this section we focus on locating the Storm blocks in Peer-to-Peer environment. We don't |
In this section we focus on locating the Storm blocks in Peer-to-Peer environment. We don't |
1791 |
respond to fetching of Storm blocks as fetching of Storm block can be performed easily once |
respond to fetching of Storm blocks as fetching can be performed easily once |
1792 |
Storm block is located. |
Storm block is located. |
1793 |
|
|
1794 |
In chapter 2, we discussed main differences between the loosely and the tightly structured |
In chapter 2, we discussed main differences between the loosely and the tightly structured |
1802 |
originator is located in the overlay.}. To summarize, the tightly structured approach |
originator is located in the overlay.}. To summarize, the tightly structured approach |
1803 |
is more efficient and scalable than the loosely structured approach. |
is more efficient and scalable than the loosely structured approach. |
1804 |
|
|
1805 |
Since both Storm and tightly structured overlays use globally unique identifiers for each, |
Since both Storm and tightly structured overlays use globally unique identifiers for each data item, |
1806 |
it is feasible to use tightly structured overlays for \emph{locating} Storm blocks efficiently. |
it is feasible to use tightly structured overlays for \emph{locating} Storm blocks efficiently. |
1807 |
Another key feature of tightly structured overlays is that they are able |
Another key feature of tightly structured overlays is that they are able |
1808 |
to provide general purpose \emph{interface} for Reference Resolution Services (RRS) |
to provide general purpose \emph{interface} for Reference Resolution Services (RRS) |