docs: qui traite une inbox, acteur par acteur — et watch absorbe sans classer
This commit is contained in:
@@ -23,9 +23,11 @@
|
||||
*
|
||||
* ── Watching is not applying ──────────────────────────────────────────────
|
||||
* `inbox.watch` looks like this and is not: it NOTIFIES an application that made a call and
|
||||
* named one inbox, and it applies nothing. This applies, on the whole set, without anybody
|
||||
* asking — because processing an inbox is the library's job and not the app's, which is the
|
||||
* same ruling `connect.ts` opens with.
|
||||
* named one inbox. Its read does absorb the caps it passes over into memory for the session
|
||||
* — that much is unavoidable, reading is what surfaces them — but it FILES nothing durably,
|
||||
* which only `processInbox` does. This applies, on the whole set, without anybody asking —
|
||||
* because processing an inbox is the library's job and not the app's, which is the same
|
||||
* ruling `connect.ts` opens with.
|
||||
*
|
||||
* ── Subscription, never a poll ────────────────────────────────────────────
|
||||
* Every half is push-driven. The inboxes themselves are subscribed to individually. WHICH
|
||||
|
||||
Reference in New Issue
Block a user