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

HTTP Provider Resumability #281

Open
hannahhoward opened this issue Jun 1, 2023 · 1 comment
Open

HTTP Provider Resumability #281

hannahhoward opened this issue Jun 1, 2023 · 1 comment

Comments

@hannahhoward
Copy link
Collaborator

Goals

Even with the fix in #280, we still fail fetches for cids on .storage that are >1GB. This introduces an interesting question around resumability of HTTP downloads for large requests. It seems to me we can accomplish this with entity-bytes if the remote supports it, but we also don't have full support yet for that in traversal. Also, Web3.storage doesn't support it.

@rvagg
Copy link
Member

rvagg commented Sep 29, 2023

I reckon this might be a candidate for Trustless Gateway spec extension, maybe even using the ipld path to specify the resumption block: ?resumePath=/path/to/block/i/want/next, or just resumeFrom=bafy... and give the next CID I want to fetch. Having the ability to do this might even open up possibilities in parallelising HTTP retrievals.

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

No branches or pull requests

2 participants