Go to file

Sean McArthur 13741f5145 fix(client): never call connect if idle connection is available

The HttpConnector's connect future was lazy, but if any custom connector
did not use a lazy future, then a connect would always be started, even
if an idle connection was available.

2018-02-28 14:18:37 -08: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

perf(http): utilize writev when possible

2018-01-25 14:02:11 -08:00

examples

fix(server): Make sleep_on_errors configurable and use it in example

2018-02-24 16:19:01 +01:00

src

fix(client): never call connect if idle connection is available

2018-02-28 14:18:37 -08:00

tests

fix(client): never call connect if idle connection is available

2018-02-28 14:18:37 -08:00

.appveyor.yml

chore(ci): update appveyor to use stable instead of nightly

2017-06-08 13:43:43 -07:00

.gitignore

init

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

.travis.yml

chore(ci): don't build docs on rust 1.18

2018-02-21 13:45:54 -08:00

Cargo.toml

v0.11.20

2018-02-26 15:07:38 -08:00

CHANGELOG.md

v0.11.20

2018-02-26 15:07:38 -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): "1.0 milestone" => "milestones"

2018-01-26 12:34:05 -08: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.