| commit | ac23b9f207c7575e25e4da57b5ea6d5172bde4fd | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <[email protected]> | Tue Aug 20 17:59:11 2024 +0000 |
| committer | Android Build Coastguard Worker <[email protected]> | Tue Aug 20 17:59:11 2024 +0000 |
| tree | f8433054006ec71b7bd3b147969274761558b45d | |
| parent | c3524e6b9d34dba900905bbc640742cdf4836bfd [diff] | |
| parent | 018c2f71bc0491217972afce01360ca8db3a98bd [diff] |
Snap for 12252487 from 018c2f71bc0491217972afce01360ca8db3a98bd to simpleperf-release Change-Id: Id87c0021fb04cc0be3783f4d0ac21ba302c00964
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.
