75eecc476c
This changes the Service request type to a generic instead of an associated type. This is more appropriate as requests are inputs to the service. This change enables a single implementation of `Service` to accept many kinds of request types. This also enables requests to be references. Fixes #99
Tower Service
The foundational Service trait that Tower is based on.
Overview
The Service trait provides the foundation upon which Tower is built. It is a
simple, but powerful trait. At its heart, Service is just an asynchronous
function of request to response.
fn(Request) -> Future<Item = Response>
Implementations of Service take a request, the type of which varies per
protocol, and returns a future representing the eventual completion or failure
of the response.
Services are used to represent both clients and servers. An instance of
Service is used through a client; a server implements Service.
By using standardizing the interface, middleware can be created. Middleware
implement Service by passing the request to another Service. The
middleware may take actions such as modify the request.
License
This project is licensed under the MIT license.
Contribution
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in Tower by you, shall be licensed as MIT, without any additional terms or conditions.