Seize
An atomic seize: when an entity arrives, the station either acquires amount units of resource (recording the Allocation with the network so ReleaseStation can release it later) and forwards the entity, or blocks the entity in its own queue. When the resource gains units, the station serves as many waiting entities as it can.
Between this station and a paired ReleaseStation, the entity continues to hold the allocation across any number of intermediate stations. This is the Arena-style separation of seize / delay / release that lets a single entity hold multiple resources simultaneously (e.g., tester + machine).
Several seize stations may share the same resource; each has its own queue and reacts to the resource's availability event in registration order (first-come tie-break).
Construct via StationNetwork.seizeStation or the builder DSL.
Properties
True if this node has any onward routing configured (a static next receiver, a station-level sender, or a class route). A non-terminal node for which this is false — and which is not a non-terminal step of a registered route — is a dangling node and fails validation.
The number of times this station successfully seized the resource.
The waiting queue of entities blocked at this seize station.
Functions
Sets the receiver of entities that have just seized the resource.
The statically known receivers this node may route to. Best-effort: empty when the node has no static link or when its routing is opaque (for example, a probabilistic sender whose destinations are not introspectable).