Add a PeerRouting.FindPeerAsync function
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.9k
- Forks
- 1.3k
- Avg merge
- 13d 21h
- Merged PRs (30d)
- 1
Description
There's a FindProvidersAsync, there will soon be a GetValuesAsync, but there is no GetPeerAsync. With a GetPeerAsync, we could try peer addresses as we find them instead of waiting for the search to complete. Benefits over the current system:
* Can abort searches early (save bandwidth)
* Can keep searching until we find an address for the peer that works (reliability).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the existing PeerRouting and FindProvidersAsync behavior, then compare it with the planned GetValuesAsync API. Define how GetPeerAsync should expose peer addresses as they are found so callers can abort early or continue until a working address is found; done means the new function supports both behaviors consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100