-
Notifications
You must be signed in to change notification settings - Fork 17
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
Share SP selection logic with HTTP #197
Comments
Merged
rvagg
added a commit
that referenced
this issue
May 18, 2023
rvagg
added a commit
that referenced
this issue
May 18, 2023
rvagg
added a commit
that referenced
this issue
May 18, 2023
rvagg
added a commit
that referenced
this issue
May 23, 2023
rvagg
added a commit
that referenced
this issue
May 23, 2023
rvagg
added a commit
that referenced
this issue
May 23, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What
After we improve SP Selection logic with #92 for GraphSync (probably just the initial version), we should port this logic over to the HTTP protocol. (#193)
Implementation
Somewhat open ended -- let's collect the bare minimum information needed to match whatever we're currently aiming to collect with graphsync (I think just correctness for starters), and use it to put the PriorityWaitQueue into the HTTP selector. In this case, there's no "connect" step so we're just ranking all the providers at once and then selecting one semi randomly.
The text was updated successfully, but these errors were encountered: