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

Decide on how to disambiguate IPLD pathing from IPFS pathing #248

Closed
Stebalien opened this issue Jun 13, 2017 · 2 comments
Closed

Decide on how to disambiguate IPLD pathing from IPFS pathing #248

Stebalien opened this issue Jun 13, 2017 · 2 comments
Labels

Comments

@Stebalien
Copy link
Member

Stebalien commented Jun 13, 2017

Currently, the IPFS daemon plays it fast-and-loose with pathing and uses the CID (whether or not the object is stored as a protobuf) to decide on whether to path through it as an IPFS directory tree or an IPLD object.

Instead, we may want to consider using a /ipld/... prefix. We definitely should not be disambiguating based on the CID as the object encoding should have no bearing on how we path through it once we've decoded it.

@daviddias
Copy link
Member

I feel this Q should go into a discussion on https://github.com/ipld/specs. Nevertheless, I agree with the /ipld pathing, I believe @whyrusleeping does too.

@Stebalien
Copy link
Member Author

Turns out we already have such a discussion: ipld/specs#8

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

No branches or pull requests

2 participants