Make H2/H1 Limits tunable from Python
- Dominant language
- Zig
- Stars
- 55
- Forks
- 2
- Avg merge
- 9h 52m
- Merged PRs (30d)
- 69
Description
Both \`Reader.init\` (H1) and \`H2Connection.init\` use hardcoded defaults (\`connection_obj.zig:381,399\`); \`parseArgs\` only reads \`role\`/\`protocol\`. THREAT_MODEL says \"tune Limits for the deployment\" but the API makes it impossible - the anti-DoS knobs are unreachable.
**Fix:** add a \`limits=\` constructor kwarg.
Tier 2. Effort: M.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading connection_obj.zig around Reader.init and H2Connection.init, then inspect parseArgs and the THREAT_MODEL guidance on tuning Limits. Trace how constructor keyword arguments reach these initializers. Done means a limits= keyword can configure the H1 and H2 anti-DoS limits instead of using only hardcoded defaults.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, zig
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 70/100