True while an ordering application is in flight for geometry
(including while a held newest ordering is waiting its turn).
This is NOT a dispatch gate. It once was — no new sort was dispatched
for a node while a stream ran, because a stream wrote into the LIVE
attribute and sorting faster than it could apply just churned held
orderings. Now that a stream writes into the inactive buffer, the
displayed ordering is complete throughout, so sorting and applying
proceed CONCURRENTLY; the only thing bounding sort traffic is the
one-in-flight-per-node rule.
True while an ordering application is in flight for
geometry(including while a held newest ordering is waiting its turn).This is NOT a dispatch gate. It once was — no new sort was dispatched for a node while a stream ran, because a stream wrote into the LIVE attribute and sorting faster than it could apply just churned held orderings. Now that a stream writes into the inactive buffer, the displayed ordering is complete throughout, so sorting and applying proceed CONCURRENTLY; the only thing bounding sort traffic is the one-in-flight-per-node rule.