Allow peerstore to write to a go-datastore

[csasarak]

I am working with @whyrusleeping to allow peerstore data to be stored to the hard disk when it takes up a certain amount of space as described in go-ipfs issue #2484

I'm opening this issue to discuss adding support for the go-datastore interface.

[jbenet]

wonder if we should reuse the record abstraction here @diasdavid? Basically
peerstore, providers, and so on all storing records and internally they can
be given a recordstore implementation backed by a go-datastore to store to
disk. Would seriously simplify the abstraction creep in all the modules.
(I.e. Only one module would know why a datastore is a thing).

I think @diasdavid already does something like this, or has suggested it in
the past.
On Wed, Aug 17, 2016 at 20:33 Christopher Sasarak [email protected]
wrote:

I am working with @whyrusleeping https://github.com/whyrusleeping to
allow peerstore data to be stored to the hard disk when it takes up a
certain amount of space as described in go-ipfs issue #2484
ipfs/kubo#2848

I'm opening this issue to discuss adding support for the go-datastore
interface.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#90, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIcoSeNGrypxq91fZkrKBJ9EzCFvUGBks5qg6hlgaJpZM4JnBaw
.

[daviddias]

do we need to sign the peer info objects? storing them as records would mean that, which might be a good thing and also, would write them to disk with some validity property.

[bigs]

I'm gonna take a go at this! There already seems to be some work done on the go-libp2p-peerstore project, though it seems quite stale. If I don't hear anything about reviving that change, I'll probably start fresh (taking ideas/inspiration from that PR) tomorrow.

Edit: Tagging @csasarak!

[Stebalien]

This exists now.