Skip to main content

Module in_process

Module in_process 

Source
Expand description

The in-process transport. The in-process transport: a request in, a response out, no socket.

§Why there are two transports

The core in crate::document answers a request against a document. How the request arrives is a separate question, and it has two answers.

crate::server is one of them: a Unix socket, MCP framing, a listener on its own thread. That is how a QA harness and an agent outside the process reach a running application, and it is the transport eleven fleet sites are driven over.

This is the other. An embedder that already holds the document calls straight in. There is no socket to bind, no descriptor to publish, no serialisation, and no second thread. AgencyZero is about to be both at once: agents drive it over the socket while it drives a browser it embeds, in process, through this.

§What this adds over calling the core directly

State that one request leaves for the next, and which the core deliberately does not hold: the document revision an Inspect reports, the pointer position an injected wheel event needs, which buttons an injected pointer is holding down, and the reusable offscreen surface a capture draws into.

It also holds the action dispatch itself. That existed twice, once in the Tauri runtime and once in the headless browser, and the two had already diverged: one replaced a text field’s contents by selecting them and the other by counting bytes, and only the second works with no font catalogue installed. See DocumentControl::act.

Structs§

DocumentControl
One document, driven in process.

Functions§

settle
Drain the synchronous script work an action caused.