Consider Exposing an AsyncRead/AsyncWrite-based Interface
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.3k
- Forks
- 1.8k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 14
Description
I'd like to request that Hyper exposes an AsyncRead/AsyncWrite-based interface—effectively, the current proto module—in Hyper as a lower-level alternative than the conn interfaces and higher level than the httparse interfaces. I see two main benefits for this interface: it provides a low-level escape hatch for projects that might build atop of Hyper's infrastructure, but it also provides an interesting learning opportunity for readers.
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 reading Hyper's current proto module alongside the conn and httparse interfaces named in the issue. Define the scope and API shape for exposing an AsyncRead/AsyncWrite-based lower-level interface, with completion shown by a reviewed public interface and documentation for its intended use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100