Re: [Gzz-commits] manuscripts/storm article.rst

[hemppah]

Quoting Benja Fallenstein <address@hidden>:

> CVSROOT:      /cvsroot/gzz
> Module name:  manuscripts
> Changes by:   Benja Fallenstein <address@hidden>      03/01/25 13:34:09
> 
> Modified files:
>       storm          : article.rst 
> 
> Log message:
>       start section on block storage
> 
> +Collections of Storm blocks are called *pools*. Pools provide
> +the following interface::
> +
> +    getIds() -> list
> +    get(id) -> block
> +    add(block)
> +    delete(block)
> +
> +Implementations may store blocks in RAM, in individual files,
> +in a Zip archive, in a database or through other means.
> +We have implemented the first three (using hexadecimal
> +representations of the block ids for file names).

Does this mean that that one pool can reside only on one computer ? Or, can one
pool reside on multiple computer ?

If used in one computer, we might use CFS-like self-certifying structures:
identify pool by key and pool's block's by content hashes of blocks. As stated
in CFS article, 'they can check the integrity of the root block using that key,
and the integrity of blocks lower in the tree with the content hash identifiers
that refer to those block.'

CFS uses hierarchical approach (directory-tree like, SFS), but I wonder, if we
can create 'Storm like' design&implementation from this idea: identify pool by
key and pools blocks by content hash, or something like that.


-Hermanni

-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/