2 releases

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

#5 in #named-pipe

Download history 20544/week @ 2024-12-25 27756/week @ 2025-01-01 37608/week @ 2025-01-08 39985/week @ 2025-01-15 41369/week @ 2025-01-22 49368/week @ 2025-01-29 57786/week @ 2025-02-05 52857/week @ 2025-02-12 56769/week @ 2025-02-19 57157/week @ 2025-02-26 54671/week @ 2025-03-05 74283/week @ 2025-03-12 66854/week @ 2025-03-19 68394/week @ 2025-03-26 65379/week @ 2025-04-02 62632/week @ 2025-04-09

281,170 downloads per month
Used in 58 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–13MB
~148K SLoC