#named-pipe #hyper-client #pipe #hyper #hyper-http #named

hyper-named-pipe

Hyper client bindings for Windows Named Pipes

2 releases

0.1.0 Jan 24, 2024
0.1.0-rc1 Jan 20, 2024

#174 in HTTP client

Download history 504/week @ 2024-02-27 2029/week @ 2024-03-05 2950/week @ 2024-03-12 4616/week @ 2024-03-19 3495/week @ 2024-03-26 5658/week @ 2024-04-02 5409/week @ 2024-04-09 4918/week @ 2024-04-16 7219/week @ 2024-04-23 7536/week @ 2024-04-30 7407/week @ 2024-05-07 9515/week @ 2024-05-14 10325/week @ 2024-05-21 10725/week @ 2024-05-28 10873/week @ 2024-06-04 9932/week @ 2024-06-11

43,256 downloads per month
Used in 62 crates (2 directly)

Apache-2.0

11KB
125 lines

crates.io license appveyor docs

Hyper-named-pipe: Hyper client bindings for Windows Named Pipes

Exposes a HTTP interface over Tokio's Named Pipes implementation through a Hyper Connection interface.

Install

Add the following to your Cargo.toml file

[dependencies]
hyper-named-pipe = "*"

Usage

Ensure host's are hex-encoded when passed into HyperUri as this will bypass validation.

let pipe_name = r"\\.\pipe\named-pipe";

let builder = Client::builder(TokioExecutor::new());
let client: Client<NamedPipeConnector, Full<Bytes>> = builder.build(NamedPipeConnector);

let host = hex::encode(pipe_name);
let uri_str = format!("{}://{}", NAMED_PIPE_SCHEME, host);
let url = uri_str.parse().expect("Invalid URI");

async move {
  client.get(url).await.expect("Unable to fetch URL with Hyper client");
};

Tests

It's possible to run the unit test on a unix platform using the cross helper:

cross test --target i686-pc-windows-gnu

Dependencies

~5–14MB
~149K SLoC