Design 47 H: H-A-305, one renderer: the node-engine renders the allowances it asks of the holder
This commit is contained in:
@@ -1793,3 +1793,12 @@ Where two preparers disagreed, the chosen one is named.
|
||||
said. The decision record amending ADR 0170 and the design lines in 08 §4 and 33 are written beside the build
|
||||
(hq-record-writer, hq-design-writer). First use: tcp 8000 on the operator's desktop's LAN interfaces. P7,
|
||||
tools-are-how-a-module-is-spoken-to.
|
||||
- **H-A-305 (one renderer: the node-engine renders the allowances it asks of the holder, 20:26)** Amends H-A-304: the
|
||||
node-engine stays the one renderer of the filter file (nothing else writes the input chain); at every compose of
|
||||
the filter it asks the holder's allowed verb and renders the allowances beside the ports derived from the modules'
|
||||
listens; the holder keeps the allowances in its own state and says every change as the event
|
||||
node-packet-filter.allowances-changed, which the node-engine hears to compose the filter again; an expired
|
||||
allowance is left out by the holder's answer and said by it. The holder's state is asked for in its manifest's
|
||||
requires by the state template; if the TypeScript SDK does not yet give a module a state, that gap is built in the
|
||||
SDK first (mesh-sdk ts), not worked around. P-NATS-native (events first; a call where an answer is needed; a
|
||||
module's state reached by its owner), P7 (one renderer), P3.
|
||||
|
||||
Reference in New Issue
Block a user