Class TriggerAcquisitionResult

What AcquireNextTriggersAndFireDue(TriggerAcquisitionRequest, CancellationToken) acquired: the triggers it fired as it acquired them, what became of each, and the ones it left for the scheduler to fire when they are due.

public sealed class TriggerAcquisitionResult

Inherited Members: object.Equals(object)

object.Equals(object, object)

object.GetHashCode()

object.GetType()

object.ReferenceEquals(object, object)

object.ToString()

Remarks

Due and Fired are index-aligned, as a TriggersFired(IReadOnlyCollection<IOperableTrigger>, CancellationToken) batch is with its results, and the scheduler reads each pair the way it reads that batch: it runs a fired bundle, releases a trigger that did not fire or failed to, and leaves a declined one alone.

A property left unset reads as an empty list, so a store that fires nothing on acquisition sets Pending alone.

The acquired triggers the store fired as it acquired them, in the order it fired them.

public List<IOperableTrigger> Due { get; init; }

What became of each trigger in Due, at the same index: what TriggersFired(IReadOnlyCollection<IOperableTrigger>, CancellationToken) would have answered for it.

public List<TriggerFiredResult> Fired { get; init; }

The acquired triggers not fired yet, in fire-time order. The scheduler waits for the first of them and fires them with TriggersFired(IReadOnlyCollection<IOperableTrigger>, CancellationToken), as it does what AcquireNextTriggers(TriggerAcquisitionRequest, CancellationToken) returns.

public List<IOperableTrigger> Pending { get; init; }

Like that list, this one may be one the store keeps: the scheduler copies it before working with it.