1782 |
As we discussed already in chapter 4, Fenfire's Storm design |
As we discussed already in chapter 4, Fenfire's Storm design |
1783 |
uses SHA-1 \cite{fips-sha-1} hash over the contents of a scroll block for creating globally unique |
uses SHA-1 \cite{fips-sha-1} hash over the contents of a scroll block for creating globally unique |
1784 |
identifiers for each scroll block. In our scenario, fragments of data is distributed |
identifiers for each scroll block. In our scenario, fragments of data is distributed |
1785 |
throughout the Peer-to-Peer overlay. Our task is to locate and fetch |
throughout the Peer-to-Peer overlay. We want that user operations in Fenfire are location transparent. |
1786 |
(i.e. obtain) \emph{all} Storm scroll blocks, associated to a specific ''virtual |
Therefore, our task is to locate and fetch (i.e. obtain) \emph{all} Storm scroll blocks, associated to a specific ''virtual |
1787 |
file'', from Peer-to-Peer overlay as efficiently as possible. In addition to |
file'', from Peer-to-Peer overlay as efficiently as possible. In addition to |
1788 |
\emph{direct} scroll block obtaining using globally unique identifier of Storm scroll block, |
\emph{direct} scroll block obtaining using globally unique identifier of Storm scroll block, |
1789 |
we also must support \emph{indirect} obtaining of Storm scroll block using pointer blocks. |
we also must support \emph{indirect} obtaining of Storm scroll block using pointer blocks. |