Answer A-423: one reader per durable through the hub; a consumed kept event with no route is said
This commit is contained in:
@@ -1076,3 +1076,10 @@ the principle that settles it, cited as "design 47 G A-n".
|
||||
a stream it cannot bind is said in its log and its start goes on. The replay of what waited is heard as any event;
|
||||
a part whose handler cannot take its backlog is a finding of the change, read before its delivery. (Thorough fix,
|
||||
said: the indexer's own call, b0242f68, is the quick fix placed meanwhile.)
|
||||
- **A-423** (A-397, A-422; read from the code 2026-11-15: the assigner reads machine-away and machine-back, and the forge
|
||||
bridge branch-moved, with readers of their own on the durable the hub now binds too, so each message would reach one
|
||||
of the two; and the checker, the forge bridge, the view and distribution consume registration-changed in their
|
||||
manifests with no route, so its durable fills unread; principles 1, 3 and 7) One reader per durable: the hub is the
|
||||
only reader of a part's kept streams, and a part that read one itself hands its handler to the hub, which gives each
|
||||
event to every handler it has for it. A kept event a part's manifest consumes and no route takes is said at its start,
|
||||
naming the event, as a fault of the part to be fixed in its manifest or its code.
|
||||
|
||||
Reference in New Issue
Block a user