-
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
support header specifying additional root cid #192
Labels
enhancement
New feature or request
Comments
Notes: We can probably kick off a second HTTP request in the content routing subsystem to IPNI and just combine the two streams and use the CandidateBuffer to combine the streams |
Assuming this is coming in through the Gateway->Saturn path, how is the second CID originating from the source requestor in that flow? Is it something like an upstream component having part of the DAG but wanting to fill in holes? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
there may be a 'higher' root cid than the one requested that the client suggests will be more useful for finding peers only advertising their root CIDs.
This CID may be communicated in a header - lassie should do a content routing lookup also for this cid when present.
The text was updated successfully, but these errors were encountered: