Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add DAG Protobuf Support #51

Merged
merged 1 commit into from Dec 3, 2019
Merged

Add DAG Protobuf Support #51

merged 1 commit into from Dec 3, 2019

Conversation

hannahhoward
Copy link
Collaborator

Follow-up to auto closed pull request #46 -- now rebased on the feat/response hooks -- please see that PR for previous discussion

Copy link
Member

@Stebalien Stebalien left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So, having to link-in the DagPB IPLD codec this way smells but fixing it now would unnecessarily block this.

@warpfork and @hannahhoward, could you work together to figure out a clean way to avid this? Maybe:

  • Have a registry of node builders?
  • Have codecs specify supported/default node builders?
  • Create an even more basic default node builder such that implementing DagPB with this node builder isn't painful?

I'm not familiar enough with the architecture to make any specific suggestions.

@hannahhoward hannahhoward changed the base branch from feat/response-hooks to master December 3, 2019 00:37
Incorporate go-ipld-prime-proto and write test to verify that graphsync works with it
@hannahhoward hannahhoward merged commit 7f8d961 into master Dec 3, 2019
@mvdan mvdan deleted the feat/dag-protobuf branch December 15, 2021 14:15
marten-seemann pushed a commit that referenced this pull request Mar 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants