Skip to content
This repository has been archived by the owner on Mar 28, 2023. It is now read-only.

Use separate namespace for IPNS cache #1612

Closed
cpacia opened this issue May 29, 2019 · 1 comment · Fixed by #1637
Closed

Use separate namespace for IPNS cache #1612

cpacia opened this issue May 29, 2019 · 1 comment · Fixed by #1637
Assignees

Comments

@cpacia
Copy link
Member

cpacia commented May 29, 2019

Our ipfs package adds a persistent cache layer on top of IPNS. The data is stored in the ipfs db. However, we are currently having a namespace collision with the DHT package which uses the datastore to store some of it's records.

We need to create a separate namespace for our cache.

@cpacia cpacia self-assigned this May 29, 2019
cpacia added a commit that referenced this issue May 29, 2019
Our IPNS package implements a separate persistent cache for IPNS records. The
format of the value stored in the database is different from the format used
by the DHT package. This commit changes the database key used by the persistent
cache to make sure it does not collide with the key used by the DHT package
which might otherwise cause records to be overriden with a different format.

closes #1612
placer14 pushed a commit that referenced this issue Jun 3, 2019
Our IPNS package implements a separate persistent cache for IPNS records. The
format of the value stored in the database is different from the format used
by the DHT package. This commit changes the database key used by the persistent
cache to make sure it does not collide with the key used by the DHT package
which might otherwise cause records to be overriden with a different format.

closes #1612
@placer14
Copy link
Member

This is merged and being delivered with v2.3.4. Closing as resolved.

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

Successfully merging a pull request may close this issue.

2 participants