| commit | fd4bf87bf61750714d08027078b85f8c464d4dfc | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <[email protected]> | Thu Aug 08 01:12:43 2024 +0000 |
| committer | Android Build Coastguard Worker <[email protected]> | Thu Aug 08 01:12:43 2024 +0000 |
| tree | 370f6d116b37bb85ffe691cda82f9a480b4eef88 | |
| parent | 8e0d2bda09608986d880fa72fe163d1277a06b76 [diff] | |
| parent | 9adedc8c0e013676663d8c4965d37291d4817ec8 [diff] |
Snap for 12199973 from 9adedc8c0e013676663d8c4965d37291d4817ec8 to 24Q4-release Change-Id: Ia365a586be2b964e5ff971989dea2b0cfb5f3792
A connect, read and write timeout aware connector to be used with hyper Client.
At the time this crate was created, hyper does not support timeouts. There is a way to do general timeouts, but no easy way to get connect, read and write specific timeouts.
There is a TimeoutConnector that implements the hyper::Connect trait. This connector wraps around HttpConnector or HttpsConnector values and provides timeouts.
Note: In hyper 0.11, a read or write timeout will return a broken pipe error because of the way tokio_proto::ClientProto works
Hyper version compatibility:
master branch will track on going development for hyper.0.4 release supports hyper 0.14.0.3 release supports hyper 0.13.0.2 release supports hyper 0.12.0.1 release supports hyper 0.11.Assuming you are using hyper 0.14, add this to your Cargo.toml:
[dependencies] hyper-timeout = "0.4"
See the client example for a working example.
Licensed under either of
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.