Module record_content
Expand description
The content a record references: its lanes and stores are the collab
client’s (collaboration::record_content); what a view reads of it, as
arrivals, is the toolkit’s.
Structs§
- Content
Lane - Where one record’s content store and its window’s collaboration meet.
- Content
Reads - The content a view shows, each address a read
(
crate::arriving::Arriving): ready once its bytes are on this device (read them from the store), pending while it is on its way from the workspace’s host (crate::workspace_sync::source), failed when no device has it. Content this device has is ready on the first read, so a view of it opens complete. - Content
Unavailable - Content a record references that cannot arrive: every device that could hand it over said it keeps none.
- Lane
Requests - What the window sends on the record’s route.
- Record
Content - A record’s content store: the store a host lent the app, with content the record references travelling on the record’s route.
Constants§
- MAX_
RECORD_ CONTENT_ BYTES - Largest content one record references.
Functions§
- arrivals
- How many times content has reached a record’s store in this process: arrived on a record’s route, or stored by an app. A window that lacks content its record references reads again when this has moved since it last looked; it never looks on a timer.
- keep_
lane - Let
window’s record content travel onlane: the window keeps it, and its own record content reads it back (ContentLane::of_window).