Zoran Vasiljevic schrieb:
For my *personal* taste, the API is way too large
but what I do not use, I do not care for.
I have nothing against having all this in core
and I have nothing against maintaining this
code in future, if the need arises.
The ns_cache interface resembles much similarity to the nsv interface.
Essentially, it looks to me
as an outsider that the main difference to nsv are the options for pool
size and timeout. Has anyone
considered to converge nsv and ns_cache by e.g. providing storage pools
with size and timeout
to nsv (binding nsv varnames to storage pools)? Also, the eval
subcommand makes sense for
nsv.
-gustaf
