| commit | d048fd3d219fc81511934b8a9fc1310cf9c09174 | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <[email protected]> | Sat Sep 21 01:16:15 2024 +0000 |
| committer | Android Build Coastguard Worker <[email protected]> | Sat Sep 21 01:16:15 2024 +0000 |
| tree | 8e0200c672a550de7abd4ad42d24547c9a369027 | |
| parent | dcb3d79baf933eedb7d77d957fc278eb50062d88 [diff] | |
| parent | 3b350dee37b33512117ea9a4975d30728ebb9ebc [diff] |
Snap for 12397640 from 3b350dee37b33512117ea9a4975d30728ebb9ebc to 24Q4-release Change-Id: I823723c2cc84c46a92606082064862805facd656
The foundational Service trait that Tower is based on.
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.
async fn(Request) -> Result<Response, Error>
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.
This project is licensed under the MIT license.
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.
