30870029b9
This adjusts the way `Service`s are created for a `hyper::Server`. The `MakeService` trait allows receiving an argument when creating a `Service`. The implementation for `hyper::Server` expects to pass a reference to the accepted transport (so, `&Incoming::Item`). The user can inspect the transport before making a `Service`. In practice, this allows for things like getting the remote socket address, or the TLS certification, or similar. To prevent a breaking change, there is a blanket implementation of `MakeService` for any `NewService`. Besides implementing `MakeService` directly, there is also added `hyper::service::make_service_fn`. Closes #1650
28 lines
787 B
Rust
28 lines
787 B
Rust
#![deny(warnings)]
|
|
extern crate hyper;
|
|
extern crate pretty_env_logger;
|
|
|
|
use hyper::{Body, Request, Response, Server};
|
|
use hyper::service::service_fn_ok;
|
|
use hyper::rt::{self, Future};
|
|
|
|
fn main() {
|
|
pretty_env_logger::init();
|
|
let addr = ([127, 0, 0, 1], 3000).into();
|
|
|
|
let server = Server::bind(&addr)
|
|
.serve(|| {
|
|
// This is the `Service` that will handle the connection.
|
|
// `service_fn_ok` is a helper to convert a function that
|
|
// returns a Response into a `Service`.
|
|
service_fn_ok(move |_: Request<Body>| {
|
|
Response::new(Body::from("Hello World!"))
|
|
})
|
|
})
|
|
.map_err(|e| eprintln!("server error: {}", e));
|
|
|
|
println!("Listening on http://{}", addr);
|
|
|
|
rt::run(server);
|
|
}
|