-
Notifications
You must be signed in to change notification settings - Fork 35
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
IPLD Resolver: Service #465
Closed
Labels
Comments
This was referenced Feb 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Part of #475
Create an IPLD Resolver Service that:
Swarm
with an IPLD Resolver Behaviour wrapping Add sorting imports #34 IPLD Resolver: Membership #467 and IPLD Resolver: Content #466run
method to start listening on an address and poll theSwarm
for eventsMembership
raises an event about an agent serving a new subnet it didn't know about before, then the service would promptDiscovery
to look up its peer ID to ensure it has the address if needed.Swarm
) to look for internal requests.Membership
for the list of peer IDs serving data from a topic, askDiscovery
for the list of connected/known addresses, then decide how many to pass toResolve
and in which order - connected first, known addresses last; but maybe just a few at a time to not span the network, e.g. if we know 100 agents serving data in a subnet, we can send bitswap requests to 10 of them, and if it fails, then another 10, etc. Note that theBitswap
library is clever enough to only sendwant-have
first to all-but-one, and thenwant-block
to one at a time, but we might want to keep even thewant-have
within a limit. At some point we might even ask the parent subnet members for the data - a fully Bitswap implementation would keep the wants and complete them later, but notlibp2p-bitswap
.The text was updated successfully, but these errors were encountered: