Expand description
IPC infrastructure for client-server communication
Uses the interprocess crate for cross-platform local sockets:
- Unix domain sockets on Linux/macOS
- Named pipes on Windows
Each session has two sockets: data (byte stream) and control (JSON messages).
Structs§
- Client
Connection - Client connection to server
- Server
Connection - A client connection (from the server’s perspective)
- Server
Listener - Server listener for accepting client connections
- Socket
Paths - Socket paths for a session
- Stream
Wrapper - Wrapper for LocalSocketStream that provides thread-safe sharing Uses Arc<Mutex<>> internally to allow cloning and use across threads