Appearance
Overview
Pages in this section explain the conceptual model of the Matrix Protocol without reference to any specific transport. Read these first; the other sections use the vocabulary defined here.
| Page | What it covers |
|---|---|
| What is Matrix? | One-paragraph definition; the eight-point spec; how Matrix differs from HTTP/SMTP/REST. |
| Actors | The MatrixActor base class and the six static declarations every actor uses to describe itself. |
| Subjects | Subjects as the universal naming mechanism: $inbox, $events, $state, $reply.{cid}. |
| Mounts | Logical mount paths, the difference between binding name and runtime identity. |
| Sessions | Streaming sessions, session IDs, and how multi-message conversations are structured on top of pub/sub. |
| Request/reply | The synchronous-from-the-caller idiom: send to $inbox, await response on $reply.{cid}. |
| Events | Pub/sub events on $events, ephemeral fan-out, contrast with durable streams. |
See also
- Addressing for how these concepts encode on the wire.
- Actor Invocation for the envelope shape every message uses.