... | ... | @@ -70,7 +70,7 @@ Data is synchronised and organised into discrete frames that are represented by |
|
|
* **3.1.1** Non-owner receive state storage for `persistent` data is separate and different from send state as maintained by owners.
|
|
|
* **3.1.2** One instance of `Feed` *owns* a given `Frame` id, including across a network.
|
|
|
* **3.1.3** Timestamps of received changes must be less than or equal to the timestamp of subsequently created or dispatched `Frame`s to which they are applied.
|
|
|
* **3.1.4** Data channel storage mode is respected, meaning such changes can be overridden and lost for `persistent` and `transient` modes.
|
|
|
* **3.1.4** Data channel storage mode is respected, meaning such changes can be overridden and lost for `aggregate` and `transient` modes.
|
|
|
* **3.1.5** Received changes are marked as changes in the corresponding `Frame` being formed.
|
|
|
* **3.1.6** A dispatched `Frame` is marked as `flushed`.
|
|
|
* **3.1.7** A created `Frame` is not marked as `flushed`.
|
... | ... | |