Go to file

Sean McArthur d127201ef2 feat(rt): make tokio runtime optional

A Cargo feature `runtime` is added, which is enabled by default, that
includes the following:

- The `client::HttpConnector`, which uses `tokio::net::TcpStream`.
- The `server::AddrStream`, which uses `tokio::net::TcpListener`.
- The `hyper::rt` module, which includes useful utilities to work with
  the runtime without needing to import `futures` or `tokio` explicity.

Disabling the feature removes many of these niceties, but allows people
to use hyper in environments that have an alternative runtime, without
needing to download an unused one.

2018-04-23 16:56:26 -07:00

.github

chore(github): remove note about commit message style in PR template

2017-11-08 16:35:55 -08:00

.travis

chore(ci): only publish master docs

2017-06-16 13:06:46 -07:00

benches

feat(service): introduce hyper-specific Service

2018-04-17 17:09:15 -07:00

examples

feat(rt): make tokio runtime optional

2018-04-23 16:56:26 -07:00

src

feat(rt): make tokio runtime optional

2018-04-23 16:56:26 -07:00

tests

fix(server): panic on max_buf_size too small

2018-04-19 12:27:11 -07:00

.appveyor.yml

feat(lib): convert to use tokio 0.1

2018-03-19 11:43:47 -07:00

.gitignore

init

2014-08-30 14:18:28 -07:00

.travis.yml

feat(rt): make tokio runtime optional

2018-04-23 16:56:26 -07:00

Cargo.toml

feat(rt): make tokio runtime optional

2018-04-23 16:56:26 -07:00

CHANGELOG.md

v0.11.22

2018-03-07 12:56:57 -08:00

CONTRIBUTING.md

docs(contributing): add link to easy issues

2017-10-09 09:22:01 -07:00

LICENSE

init

2014-08-30 14:18:28 -07:00

README.md

docs(README): Use HTTPS, update website link (#1496 )

2018-04-22 08:28:58 -07:00

README.md

hyper

A low-level HTTP implementation for Rust.

Get started by looking over the guides.

Overview

hyper is a fast, safe HTTP implementation written in and for Rust.

hyper offers both an HTTP client and server which can be used to drive complex web applications written entirely in Rust.

hyper makes use of "async IO" (non-blocking sockets) via the Tokio and Futures crates.

Be aware that hyper is still actively evolving towards 1.0, and is likely to experience breaking changes before stabilising. You can also see the issues in the upcoming milestones.