MULTIPLAYER
The change arrives while you are looking.
A colleague edits an amount: it shows up on your screen, with no reload and no flicker across the rest of the record.
Field by field, not page by page
A change reaches you as a targeted patch: the field touched, its new value, and the record's version number. Only what changed changes. That is what avoids the full reload that costs you your place on the page, your scroll position, and the field you were halfway through filling.
You subscribe to what you are looking at
Delivery runs over a persistent connection, not by polling the server. Your screen subscribes to what concerns it and nothing else: the open record, the visible view, the object, an agent's session, your notifications. A list learns that its projection is stale without every record having to announce itself separately.
A record
Changes to the record you are reading.
A view
Lists whose projection has just been invalidated.
An agent
The progress of a running session, as it happens.
A dropped connection loses nothing
The client remembers the position it had reached in the stream. On reconnect, it asks for what it missed and replays it in order. And when the gap is too wide to replay, it says so instead of pretending: a screen showing stale data without knowing it is more dangerous than a screen announcing that it is resynchronising.
Your agents write into the same stream
A record edited by an agent is broadcast exactly like a record edited by hand: same channel, same patch, same version number. You watch the work happen as it happens, and an agent session's progress arrives by the same route. There is no real time for humans and deferred processing for machines.
How it works
Two people on the same client record, at the same time.
You open the record. Your screen subscribes to that record's channel.
The other edits a field. The server broadcasts the patch to every subscriber, with its version number.
Your screen follows. Only the field touched is replaced. You do not lose your place.
The network drops. On reconnect, the client replays what it missed from where it was.