| commit | 124f3e294c980b12edbc3fbc3e2e4f1ea07986e3 | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <[email protected]> | Tue Sep 10 23:10:21 2024 +0000 |
| committer | Android Build Coastguard Worker <[email protected]> | Tue Sep 10 23:10:21 2024 +0000 |
| tree | 370f6d116b37bb85ffe691cda82f9a480b4eef88 | |
| parent | 02362ddee9c89db5716a2364c4108da6a1ec4734 [diff] | |
| parent | aad6cd74e534e50e6f66219cbb16f8aa049b137b [diff] |
Snap for 12349386 from aad6cd74e534e50e6f66219cbb16f8aa049b137b to sdk-release Change-Id: Idebc15173c8fa99e5b81bcfed8d4323e25dffdf0
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.