Adapters for AsyncRead and Stream?

Open
#35 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

  • #41 by @davidpdrsn — closed without merging

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust

Research direction

Start by reading the adapter in tower-http/src/serve_file.rs around the referenced line, then compare its AsyncRead-to-Body behavior with the http-body API. Review the proposed Stream<Item = Bytes> and Stream<Item = Vec> alternatives and determine the intended upstream scope and completion criteria with maintainers.

Written by the indexing model from the issue text.

Description

In tower-http we have an adapter that makes an AsyncRead into a Body https://github.com/tower-rs/tower-http/blob/serve-file/tower-http/src/serve_file.rs#L107. Is that something you'd be interested in upstreaming to http-body? Might be useful for others.

Adapters for Stream<Item = Bytes> and Stream<Item = Vec<u8>> might also be nice.

If you're interested I can submit a PR.

Dominant language
Rust
Stars
173
Forks
71
Avg merge
1d 12h
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from hyperium/http-body

All issues in hyperium/http-body

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.