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

Implementation: separate IPLD from CBOR #25

Closed
2 tasks
nicola opened this issue Sep 26, 2016 · 2 comments
Closed
2 tasks

Implementation: separate IPLD from CBOR #25

nicola opened this issue Sep 26, 2016 · 2 comments

Comments

@nicola
Copy link
Member

nicola commented Sep 26, 2016

Taken from (meeting-notes/2016-09-19-ipld.md#layers)

Most of our IPLD implementations from js-ipld to js-ipfs-ipld assume that there is only one way to encode an IPLD object and this is CBOR. However, from the new CID conversations, IPLD+CBOR is what we all have implemented.

  • Generalize our modules
  • Create a module js-ipld-cbor(-parser|-serializer)?

note: All this is of course abstracted from the IPLD modules that by default will choose to use IPLD+CBOR

@nicola nicola changed the title Implementations: separate IPLD from CBOR Implementation: separate IPLD from CBOR Sep 26, 2016
@nicola nicola mentioned this issue Oct 3, 2016
2 tasks
@nicola
Copy link
Member Author

nicola commented Nov 6, 2016

This effort is happening in JS-IPFS, needs to update the spec

@nicola
Copy link
Member Author

nicola commented Feb 3, 2017

This is basically been done!

@nicola nicola closed this as completed Feb 3, 2017
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

1 participant