-
Notifications
You must be signed in to change notification settings - Fork 0
Closed
Labels
designRequires design (architecture, protocol, specification and task list requires further work)Requires design (architecture, protocol, specification and task list requires further work)developmentStandard developmentStandard developmentr&d:polykey:core activity 1Secret Vault Sharing and Secret History ManagementSecret Vault Sharing and Secret History Management
Description
Specification
Similar to #5, I find that it shouldn't be necessary in PK to have db and vaults running their own DB. The vaults is using EFS which has to use the root DB, but the operations should be workable under a sublevel of the DB used by all of PK.
To do this, the API of js-db has to be brought into the leveldb abstract interface, that creation of sublevels is the same as creating another DB.
Another way is to just make our level call return another DB instance, but always with the option of accessing the underlying .db property for the underlying leveldb to do certain operations.
This should be done with investigating #5 so that a consistent solution can be found.
Additional context
Tasks
- ...
- ...
- ...
Metadata
Metadata
Assignees
Labels
designRequires design (architecture, protocol, specification and task list requires further work)Requires design (architecture, protocol, specification and task list requires further work)developmentStandard developmentStandard developmentr&d:polykey:core activity 1Secret Vault Sharing and Secret History ManagementSecret Vault Sharing and Secret History Management