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.

Sign up for GitHub

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

Jump to bottom

Refactor Gateway API so can extract out the request layer #173

Closed
BigLep opened this issue Feb 16, 2023 · 0 comments · Fixed by #176
Closed

Refactor Gateway API so can extract out the request layer #173

BigLep opened this issue Feb 16, 2023 · 0 comments · Fixed by #176
Assignees
@aschmahmann
Labels
topic/gateway Issues related to HTTP Gateway

Comments

@BigLep
Copy link
Contributor

BigLep commented Feb 16, 2023 •
edited by aschmahmann
Loading

Done Criteria

The Gateway API interface is updated so that it is possible to fulfill gateway requests with the content fetching and IPLD processing happening externally and the gateway code handling the HTTP portion.

Basic set of implementations of the API that need to be usable.

  • Block based (blockservice + dagservice + pathing/ipld)
  • Graph based (CAR request for data + IPLD parsing of responses)

Why Important (Now)

This unblocks work on decreasing the latency of requests for the Rhea project which impacts performance of the ipfs.io gateway.

Notes

Design is happening in https://www.notion.so/pl-strflt/WIP-go-libipfs-Gateway-API-6f6dc875e65544e58740fadd206b2e74
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aschmahmann aschmahmann

Labels
topic/gateway Issues related to HTTP Gateway
Projects
No open projects
IPFS Shipyard Team
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: refactor gateway api to operate on higher level semantics ipfs/boxo
3 participants
@BigLep @lidel @aschmahmann