Allow max_concurrent_reset_streams>0 on browser environments
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.6k
- Forks
- 382
- Avg merge
- 20h 23m
- Merged PRs (30d)
- 9
Description
I'm willing to set max_concurrent_reset_streams to a value higher than 0. In browser environments, this causes h2 to panic (see #511).
I'm willing to work on this issue. I could add a web feature enabling the optional instant dependency and being used instead of std::time::Instant to provide time. #511 was closed by a temporary fix.
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 tracing the handling of max_concurrent_reset_streams and the browser-time behavior described in issue #511. Review whether a web feature and optional instant dependency fit the existing configuration and timing design; done means values above 0 work in browser environments without the reported panic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100