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

Switch to DAG-CBOR #56

Open
lidel opened this issue Oct 13, 2022 · 0 comments
Open

Switch to DAG-CBOR #56

lidel opened this issue Oct 13, 2022 · 0 comments
Labels
kind/discussion Topical discussion; usually not changes to codebase need/analysis Needs further analysis before proceeding need/triage Needs initial labeling and prioritization P1 High: Likely tackled by core team if no one steps up

Comments

@lidel
Copy link
Member

lidel commented Oct 13, 2022 •
edited
Loading

Ref. ipfs/specs#327, tldr:

  • dag-cbor as default wire format in production (make client library always send cbor request and expect cbor response)
  • dag-json still supported for backward-compatibility and debugging
@lidel lidel added P1 High: Likely tackled by core team if no one steps up kind/discussion Topical discussion; usually not changes to codebase need/analysis Needs further analysis before proceeding need/triage Needs initial labeling and prioritization labels Oct 13, 2022
@ipfs ipfs deleted a comment from welcome bot Oct 13, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
kind/discussion Topical discussion; usually not changes to codebase need/analysis Needs further analysis before proceeding need/triage Needs initial labeling and prioritization P1 High: Likely tackled by core team if no one steps up
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lidel