Support Data Driven Configurations for Tables, Replications, etc...

[grecinto]

Today, code drives the configurations details of tables(B-trees' configurations) & replication feature(EC config, StoreInfo & Registry home folders paths). SOP needs to be able to support capturing these details into a table (e.g. confguration B-Tree).

Once this configurations table exists, the code artifacts used to create them can then be retired. So, SOP can operate in both modes, "code driven" configurations OR "data driven".

Code driven mode like SOP has today, is a first evolutionary step. Now that SOP is stable, it can be enhanced to support "data driven" configurations.

[grecinto]

Or at least support cmdline tool to display the configurations for all b-trees & the replications (active/passive store paths & EC configuration) that is in effect.

No need to be fancy, as the code is good, it accomplishes what it is meant. BUT being able to determine without code by displaying these details are good.

[grecinto]

Closing for now, as being a library, there are plenty of constructor/instantiator functions accepting parameter structures are good enough. Configs and readers are application responsibility.

Perhaps this can be revisited in the future, if there is anything that can be further simplified.