feat: Add configuration option to specify functions for pruning / opening peer connections
Open
Nobody has claimed this yet.
kind/architecture
kind/discussion
need/analysis
- Dominant language
- TypeScript
- Stars
- 2.6k
- Forks
- 546
- Avg merge
- 8h 18m
- Merged PRs (30d)
- 16
Description
As discussed with @wemeetagain and @achingbrain we should have a property on the Connection Manager Interface which accepts a function that will determine which peers should be pruned when above the maxConnections' threshold, as well as another function that will sort and determine which peers should be dialled by the dial-queue when the autoDialler is enabled.
Contributor guide
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 locating the Connection Manager Interface and the existing maxConnections, pruning, dial-queue, and autoDialler behavior. Define how the two configurable functions select peers and verify that both pruning and dialing follow their results; the issue names no specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100