Design 47 H2: H-A-441, the seat-list object and how the validator takes it
This commit is contained in:
@@ -592,3 +592,10 @@ The lead's one-line answers to the questions H2's develop and review raise (impl
|
||||
item's tries and next try with the three settings publish-pause, publish-pause-max and publish-tries; a send that
|
||||
fails is handed back (nak) with the pause as its delay, so the stream redelivers and nothing is put again; after
|
||||
publish-tries the builder terminates the item and says version-unreleased, loudly. P-NATS-native, P3, P-failure-loud.
|
||||
- **H-A-441 (the seat-list object and how the validator takes it, 01:53)** §814, §820, I6 (2). (a) The object holds the
|
||||
trunk's seat definitions resolved with their includes, a JSON array in composer.Request.Seats' form sorted by seat; its
|
||||
digest is the sha256 of those bytes, the object named by that digest, written at each trunk seat-definition-changed or
|
||||
-removed; the verb seat-list answers digest, size and object as D4 defines. (b) mesh-judge reads no bus:
|
||||
composer.Request gains `seat-list` (the object's digest), and the asker of a validate run (the assigner's validate step,
|
||||
the checker) fetches the object by that digest and fills Seats before the run, so the validator keeps its contract and
|
||||
every validate run of one seat list judges the same bytes. P3, ADR 0596.
|
||||
|
||||
Reference in New Issue
Block a user