TCP
Basic request/reply, strict ordering, raw bytes, and multi-client broadcast.
Open TCP source →Finite native programs
Rust examples
Choose one transport and one behavior. Every runnable exchange validates its peer messages and exits after the expected work.
Choose a target
UDP
Framed datagrams, raw datagrams, direct replies, and explicit peer fan-out.
Open UDP source →Unix / Windows
One shared handler over Unix streams or Windows named pipes.
Open local source →Unix workers
Worker threads accept from cloned handles to one Unix listener.
Open worker source →TLS boundary
Wrap an application-supplied, already verified TLS stream without choosing a crypto stack.
Open TLS boundary →Node + Rust
Run either language as TCP server or client and print the exact framed ping/pong messages.
Open mixed examples →Run from the repository root
TCP request / reply
cargo run --manifest-path rust/node-ipc/Cargo.toml \
--example TCPSocket -- basic server
# second terminal
cargo run --manifest-path rust/node-ipc/Cargo.toml \
--example TCPSocket -- basic clientLocal request / reply
cargo run --manifest-path rust/node-ipc/Cargo.toml \
--example unixWindowsSocket -- basic server
# second terminal
cargo run --manifest-path rust/node-ipc/Cargo.toml \
--example unixWindowsSocket -- basic clientPowerShell users can place each command on one line. Start the server before its client.
Behavior matrix
| Target | Selectors | Platforms |
|---|---|---|
TCPSocket | basic, basicSync, rawBuffer, Multi-Client-Broadcast | Linux, macOS, Windows |
UDPSocket | basic, rawBuffer, Multi-Client-Broadcast | Linux, macOS, Windows |
unixWindowsSocket | basic, basicSync, rawBuffer, binaryRawBuffer, Multi-Client-Broadcast | Unix socket or Windows named pipe |
clusterUnixSocket | server, client | Unix only |
TLSSocket | Prints the verified-stream integration boundary | Any native target with caller-supplied TLS |
Example boundaries
- Native examples are included in the crates.io package.
- The mixed Node/Rust and performance tools remain repository-only validation tooling.
basicSyncdemonstrates explicit ordered request/reply; it does not add Node's automatic queue.- Broadcast is direct iteration across validated connections or learned UDP addresses; it adds no library state.
- Windows synchronous named-pipe calls can block; automation must impose an external process deadline.
- These are native examples. There is no browser or WASM build in 14.0.0.