... | ... | @@ -130,10 +130,12 @@ Data is synchronised and organised into discrete frames that are represented by |
|
|
### 5. Remote Procedure Calls
|
|
|
|
|
|
#### 5.1 Initiating a Call
|
|
|
* **5.1.1** Call initiation occurs on a frame before `Frame` `flush`.
|
|
|
* **5.1.2** The call causes an immediate `flush` on the relevant RPC channel
|
|
|
* **5.1.3** The call cannot block.
|
|
|
* **5.1.4** A result callback must be provided if a response value is needed.
|
|
|
* **5.1.1** Each RPC call has its own channel.
|
|
|
* **5.1.2** Calls occur in a `Frame` before frame `flush`.
|
|
|
* **5.1.3** Calls are treated as `aggregate` channels to capture all calls.
|
|
|
* **5.1.4** Calls are not transmitted until the frame or channel is flushed.
|
|
|
* **5.1.5** The call cannot block.
|
|
|
* **5.1.6** A result callback must be provided if a response value is needed.
|
|
|
|
|
|
#### 5.2 Receiving a Call
|
|
|
* **5.2.1** Call triggers occur immediately before the `Frame` dispatches on non-owners.
|
... | ... | |