Module engine 

The engine driver: runs the sans-I/O messenger core against a [Backend]. The shell used to own this; it now only adds what is its own (wake, local bus, sealed files on disk).

Re-exports

pub use driver::Driver;

pub use http::clip_public;

pub use http::HttpExec;

pub use push::PushLink;

pub use push::PushedRoomEvent;

Modules

driver

One session’s engine run: requests the core releases are executed by the backend, /sync runs on a worker so a long poll does not stall everything else, answers go back into the core.

http

HTTP execution of the engine’s requests against one server: URL building (the spec prefix is kept only when the server was found to serve it), discovery, and the bearer.

push

The client’s push socket. The client opens it against the homeserver it already has. Push contract v1: metadata only (room, sender, event_id, recipient, wire_type) — never a plaintext body. The ack goes out before the event is handed to that session. This path does not POST. The client drives /sync and decrypts after the push.

Enums

News

What crate::Backend::wait_for_news saw.