1681 |
see \cite{lukka02freenetguids}, and for detailed Storm design, see \cite{fallenstein03storm}. |
see \cite{lukka02freenetguids}, and for detailed Storm design, see \cite{fallenstein03storm}. |
1682 |
|
|
1683 |
Storm (for \emph{STORage Module}) stores all data as \emph{blocks}, which |
Storm (for \emph{STORage Module}) stores all data as \emph{blocks}, which |
1684 |
are immutable byte sequences. SHA-1 cryptographic content hash function\footnote{SHA-1 is |
are immutable byte sequences. Storm \emph{assigns} a globally unique identifier to each |
1685 |
|
data block\footnote{This resembles the process how tightly structured overlay assigns a subset of keys |
1686 |
|
to each participating peer: a user has no control over the assignment process.}. SHA-1 cryptographic |
1687 |
|
content hash function\footnote{SHA-1 is |
1688 |
considered as a collision free hash function. Therefore, it is very unlikely that two different Storm data blocks |
considered as a collision free hash function. Therefore, it is very unlikely that two different Storm data blocks |
1689 |
would have same identifier.} \cite{fips-sha-1} is used |
would have same identifier.} \cite{fips-sha-1} is used |
1690 |
for creating location-independent, globally unique identifiers for blocks. Because of SHA-1 |
for creating location-independent, globally unique identifiers for blocks. Because of SHA-1 |
1804 |
For Fenfire's needs for \emph{locating} data, an important advantage of the |
For Fenfire's needs for \emph{locating} data, an important advantage of the |
1805 |
tightly structured approach over the loosely structured approach is that both tightly |
tightly structured approach over the loosely structured approach is that both tightly |
1806 |
structured systems and Fenfire use similar methods for identifying data in the |
structured systems and Fenfire use similar methods for identifying data in the |
1807 |
system, i.e., globally unique identifiers. |
system, i.e., Storm provides globally unique identifiers which can be used in the |
1808 |
|
tightly structured overlay. |
1809 |
Another key feature of tightly structured overlays is that they are able |
Another key feature of tightly structured overlays is that they are able |
1810 |
to provide general purpose \emph{interface} for Reference Resolution Services (RRS) |
to provide general purpose \emph{interface} for Reference Resolution Services (RRS) |
1811 |
\cite{balakrishnan03semanticfree}. Authors argue that next generation RRS must be |
\cite{balakrishnan03semanticfree}. Authors argue that next generation RRS must be |