Go to file

Sean McArthur 04c74ef596 feat(client): rename FutureResponse to ResponseFuture

BREAKING CHANGE: Replace any references of
  `hyper::client::FutureResponse` to `hyper::client::ResponseFuture`.

2018-05-04 15:21:59 -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

fix(examples): remove unused imports from examples/client.rs

2018-05-04 13:22:31 +03:00

src

feat(client): rename FutureResponse to ResponseFuture

2018-05-04 15:21:59 -07:00

tests

docs(client): add module level docs for hyper::client

2018-05-02 13:32:46 -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

refactor(lib): change from futures-timer to tokio-timer

2018-04-30 19:11:05 -07:00

Cargo.toml

chore(examples): update server example name to echo

2018-05-03 12:08:49 -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.