6ae5889f83
The `hyper::rt::Executor` trait allows defining custom executors to be used with hyper's `Client` and `Server`. Closes #1944 BREAKING CHANGE: Any type passed to the `executor` builder methods must now implement `hyper::rt::Executor`. `hyper::rt::spawn` usage should be replaced with `tokio::task::spawn`. `hyper::rt::run` usage should be replaced with `#[tokio::main]` or managing a `tokio::runtime::Runtime` manually.
Examples of using hyper
Run examples with cargo run --example example_name.
Available examples
-
client- A simple CLI http client that request the url passed in parameters and outputs the response content and details to the stdout, reading content chunk-by-chunk. -
client_json- A simple program that GETs some json, reads the body asynchronously, parses it with serde and outputs the result. -
echo- An echo server that copies POST request's content to the response content. -
hello- A simple server that returns "Hello World!" using a closure wrapped to provide aService. -
multi_server- A server that listens to two different ports, a differentServiceby port, spawning twofutures. -
params- A webserver that accept a form, with a name and a number, checks the parameters are presents and validates the input. -
proxy- A webserver that proxies to the hello service above. -
send_file- A server that sends back content of files using tokio_fs to read the files asynchronously. -
single_threaded- A server only running on 1 thread, so it can make use of!Sendapp state (like anRccounter). -
state- A webserver showing basic state sharing among requests. A counter is shared, incremented for every request, and every response is sent the last count. -
upgrades- A server and client demonstrating how to do HTTP upgrades (such as WebSockets orCONNECTtunneling). -
web_api- A server consisting in a service that returns incoming POST request's content in the response in uppercase and a service that call that call the first service and includes the first service response in its own response.