Transport

OLLMrpc.Transport

Description:

Server listen and connection layer for OLLMrpc.

The OLLMrpc.Transport namespace owns daemon-side sockets: Listen accept loops, Connection per peer, and helpers for Unix socket ( SocketListen) or TCP ( TcpListen). HTTP JSON RPC uses HttpServer with per-POST HttpReply write targets. Each socket connection keeps one OLLMrpc.Bin.Stream for the peer lifetime.

Example

var listen = new OLLMrpc.Transport.SocketListen(socket_path);
if (!listen.start()) {
    GLib.error("failed to listen on %s", socket_path);
}
// Incoming peers become Connection instances; use broadcast() to fan out

HTTP

var http = new OLLMrpc.Transport.HttpServer(8080);
http.start();

Content:

Classes:

Cert - The key and certificate files one program uses for HTTPS RPC.
Connection - One RPC client channel — bin read/write loop (Unix socket).
HttpClient - HTTP RPC client — POST JSON or bin + session headers.
HttpReply - Server-side write target for one HTTP POST.
HttpServer - HTTP JSON RPC server ( Soup.Server).
Listen - Server RPC entry — SocketListen; ollmfilesd adds Stdio transport.
PairPublish - mDNS publish for the pairing window.
Session - HTTP RPC session — shared bin JIT name tables, sequence, i**Stock prove (no layout overlay) after READY (2026-09-12 10:27):** ** o END** for the whole settle o** ext (do now):** fix why Live.Invoke for that preferred_width never reaches the ** layout.js override. s** hard cap until past that boundary; early-stop on `READY=1` / A4 marker. amed** RPC gap appears; then live re-prove. ️** `GI_RPC_JS_OVERRIDE_DIR` only when deliberately bisecting — prove scripts do **not** default it.
SocketListen - Unix socket Listen — one Connection per accepted client.
TcpListen - TCP loopback Listen for platforms without Unix sockets.