QUIC, HTTP/3, and WebTransport client
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 121
- Forks
- 45
- Avg merge
- 18h 43m
- Merged PRs (30d)
- 10
Description
These protocols allow some really good use cases.
Exposing a separate QUIC client is beneficial for use cases where HTTP/3 would be too bloated, but QUIC has advantages instead of TCP.
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
The issue mentions QUIC, HTTP/3, and WebTransport clients but identifies no files, tests, or entry points. Clarify which client or clients are in scope, the intended API, and the acceptance criteria before starting implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100