hyper-client-sockets
| Crates.io | hyper-client-sockets |
| lib.rs | hyper-client-sockets |
| version | |
| source | src |
| created_at | 2024-07-18 07:27:34.594635+00 |
| updated_at | 2025-01-20 18:01:15.02309+00 |
| description | A Hyper client library allowing access to Unix, VSock and Firecracker sockets |
| homepage | |
| repository | https://github.com/rust-firecracker/hyper-client-sockets |
| max_upload_size | |
| id | 1307098 |
| Cargo.toml error: | TOML parse error at line 18, column 1 | 18 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
| size | 0 |
kanpov (kanpov)
documentation
README
Hyper Client Sockets
Before hyper v1, hyperlocal was the most convenient solution to use Unix sockets for both client and server. With hyper v1, server socket support is no longer needed (just use UnixListener or VsockListener instead of TcpListener), yet hyperlocal still has it and hasn't received a release since several years.
This library provides hyper v1 client support for:
- Unix (
AF_UNIX) sockets (HyperUnixStreamimplementing hyper traits) - VSock (
AF_VSOCK) sockets (HyperVsockStreamimplementing hyper traits) - Firecracker Unix sockets that need
CONNECTcommands in order to establish a tunnel (HyperFirecrackerStreamimplementing hyper traits)
Additionally, the library supports different async I/O backends:
- Tokio using
tokio-backend async-iostack usingasync-io-backend
The backend to use when connecting can be specified with the Backend trait. Compiling with both backends enabled is supported but not recommended, and leaving the choice of backend to the user is recommended for library developers.
Lastly, the hyper-util feature provides compatibility with hyper-util's Client connection pool via hex-encoded URIs.