Make master distribute default settings to clients
- Dominant language
- Python
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Concurrency settings and rate limits and other advanced preferences could read defaults from master when connecting. I.e. if not explicitly specified on peer node, use values from master.
An open question: how to specify the client settings on master? More command line arguments (effectively double the current ones, hnnngh...), or perhaps just a `--client-defaults` that points to a JSON file with the defaults? Or maybe `--client-opts ""`.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points; start by tracing how master and peer connection settings are parsed and exchanged. Done means clients use master-provided defaults when they do not specify values themselves, with one agreed mechanism for configuring those defaults.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100