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

feat: range requests for certified assets #199

Closed
wants to merge 5 commits into from
Closed

Conversation

lastmjs
Copy link

@lastmjs lastmjs commented Feb 8, 2022

Original issue, not sure if I should move it to this repo: dfinity/certified-assets#10

This was originally pull-requested here: dfinity/certified-assets#21

I'm still cleaning up a bit and doing some testing, but I would love to get feedback. Besides minor cleanup and some possibly optional features missing as described here dfinity/certified-assets#10, I am done with the implementation of range requests.

@lastmjs lastmjs changed the title implement range requests for certified assets wip: implement range requests for certified assets Feb 8, 2022
@lastmjs lastmjs changed the title wip: implement range requests for certified assets feat: implement range requests for certified assets Feb 8, 2022
@lastmjs lastmjs changed the title feat: implement range requests for certified assets feat: range requests for certified assets Feb 8, 2022
@lastmjs lastmjs marked this pull request as draft February 8, 2022 20:49
@lastmjs
Copy link
Author

lastmjs commented Feb 9, 2022

I'm not sure how to move forward after this conversation: https://forum.dfinity.org/t/boundary-node-http-response-headers/10747/6

If the ETA on boundary nodes serving partial responses is far into the future, then I'm wondering if we can get this PR merged in the mean time, or if I should just maintain a fork for those interested in the functionality until the more scalable and robust boundary node version is deployed.

@lwshang lwshang closed this Mar 1, 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.

2 participants