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

Option to run @helia/http as Rapide #345

Open
meandavejustice opened this issue Dec 11, 2023 · 3 comments
Open

Option to run @helia/http as Rapide #345

meandavejustice opened this issue Dec 11, 2023 · 3 comments
Labels
dif/hard Having worked on the specific codebase is important effort/weeks Estimated to take multiple weeks kind/enhancement A net-new feature or improvement to an existing feature need/analysis Needs further analysis before proceeding

Comments

@meandavejustice
Copy link
Contributor

After we get #289 completed. We should look into a version/option to run as Rapide.

I'll need to spend a bit more time thinking about this and familiarizing myself with Rapide, but initial thoughts are that each gateways gets a service worker (worker thread if Nodejs). I'm assuming there is some library that provides an api which will let us treat them the same.
@achingbrain
Copy link
Member

This should be unblocked now - an RC of @helia/http is available - npm i @helia/http@next

@SgtPooki
Copy link
Member

We currently do round-robin based on a reliability function in our trustless gateway block-brokers. I'm sure we could benefit from some smarter downloading logic.

Making that functionality extensible, so users could implement their own download prioritization/parallelization, would be really cool.

Looks like some related issues will be helpful if we decide to implement some sort of Rapide in Helia:

@SgtPooki SgtPooki added dif/hard Having worked on the specific codebase is important effort/weeks Estimated to take multiple weeks kind/enhancement A net-new feature or improvement to an existing feature need/analysis Needs further analysis before proceeding labels Aug 15, 2024
@SgtPooki
Copy link
Member

Also related tangentially:

These came about after conversations between @lidel and @Jorropo to

minimize the number of requests Rapide has to do to learn about the shape of the DAG + be able to safely leverage deserialized responses from legacy/dumb gateways and http mirrors as webseeds

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
dif/hard Having worked on the specific codebase is important effort/weeks Estimated to take multiple weeks kind/enhancement A net-new feature or improvement to an existing feature need/analysis Needs further analysis before proceeding
Projects
No open projects
Helia Working Group (inactive)
Status: No status
Milestone
No milestone
Development

No branches or pull requests
3 participants
@achingbrain @SgtPooki @meandavejustice