Quoting Benja Fallenstein <address@hidden>:
address@hidden wrote:
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 ?
No, pools are just collections of blocks. There is no need to 'check the
pool,' just the hashes of individual blocks in the pool.
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.
We only need to identify the blocks as far as I can see...
What I was thinking was that if we can identify the owner of the pool, we could
use this information in some situations. For example, when performing search
with urn, how we can be sure, which one of the returned blocks is the correct
one (e.g. 'NYT front page'). If we know, to which pool a specific block belongs
to, we can make decisions from it (e.g. NYT is the owner of Storm pool,
identified by a key) and select the 'non-false/correct' block from the search
results' list.