Skip to content
This repository has been archived by the owner on Apr 4, 2022. It is now read-only.

Extraction of plumtree_metadata. #34

Open
cmeiklejohn opened this issue Feb 24, 2016 · 4 comments
Open

Extraction of plumtree_metadata. #34

cmeiklejohn opened this issue Feb 24, 2016 · 4 comments

Comments

@cmeiklejohn
Copy link
Contributor

plumtree_metadata should be it's own package, given it's an implementation of a KVS on top of the protocol -- this is not required, and may not be desired by all users of the library. (Additionally, by extracting this library, the eleveldb dependency is no longer required as part of the core protocol.)

@benoitc
Copy link

benoitc commented Feb 24, 2016

👍

@tsloughter
Copy link

Yea, I was just looking at plumtree again because I was thinking of replacing machi's naive 'send to everyone' with it but am not willing to bring eleveldb back in as a dependency :).

I'll probably look at doing this myself but wanted to check in case any work by others had already been done.

@cmeiklejohn
Copy link
Contributor Author

The Lasp fork does not have the eleveldb dependency nor the metadata store.

@tsloughter
Copy link

Oh, great!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants