Skip to main content

Module transport

Module transport 

Source
Expand description

Control-plane transport: Unix-domain sockets on Unix, named pipes on Windows.

The JSON-RPC layer only sees DaemonStream (an AsyncRead + AsyncWrite value) and DaemonListener. On Windows the “socket path” keeps its role as the session identity: the listener creates a marker file at that path and derives the pipe name from it, so every lifecycle routine that scans, probes, or removes *.sock files works unchanged on both platforms.

Structs§

DaemonListener

Functions§

connect
lock_path
Lock file that serializes daemons claiming socket.
peer_is_same_user
Only the daemon’s own uid may drive it; SO_PEERCRED is authoritative.
restrict_to_owner
Restrict a filesystem artifact to its owner. Unix applies mode; Windows relies on the per-user ACL that %LOCALAPPDATA% already carries.

Type Aliases§

DaemonStream