Class StoredMailRederivationRequest

Namespace

MailFathom.Application.Mail.Maintenance

Assembly

MailFathom.Application.dll

What asking for a re-derivation did: the run the scope now has, and what is carrying it.

public sealed record StoredMailRederivationRequest : IEquatable<StoredMailRederivationRequest>

Inheritance

object

StoredMailRederivationRequest

Implements

IEquatable<StoredMailRederivationRequest>

Inherited Members

object.Equals(object)

object.Equals(object, object)

object.GetHashCode()

object.GetType()

object.ReferenceEquals(object, object)

object.ToString()

Remarks

The two answers are separate because they can disagree in the cases that matter. A request finding a run already under way is answered with it and enqueues the segment that run is on, which is the ordinary case and is carried. A request that finds one whose job left the queue enqueues it again and is what puts the walk back in motion, while a queue too full to accept it has taken nothing away from the operator: the run stands, and asking again carries it. The one that needs a different act is a run whose segment is there and will never be attempted again, which Stopped is what names.

Constructors

StoredMailRederivationRequest(StoredMailRederivationRun, bool, StoredMailRederivationCarriage)

What asking for a re-derivation did: the run the scope now has, and what is carrying it.

Properties

Accepted

Whether this request is what started the run, rather than finding one already under way.

Carriage

What is carrying the segment the run is on, which is what the operator acts on.

Run

The run the scope has outstanding, which is the one this request started or the one it found.