Field MaximumFlagChangeRecordsPerValue

Namespace

MailFathom.Application.Mail.Mutations

Assembly

MailFathom.Application.dll

The greatest number of stores of one value the attribution reads for one changed occurrence.

public const int MaximumFlagChangeRecordsPerValue = 5

Returns

int

The greatest number of stores of one value the attribution reads for one changed occurrence.

Remarks

The budget belongs to one occurrence's one value, which is the terms the comparisons below are in: a reading of \Seen is settled against stores of \Seen and against nothing else. Both halves of that are what it has to guarantee. A budget spent across the window would let a message an agent starred and unstarred a dozen times take every slot from the message beside it; a budget spent across one occurrence's values would let the same pile of stars take the room that occurrence's own \Seen store needs. Either way the record that explains a value is dropped, that value is credited to the mailbox owner, and the rule that wrote it re-fires on the mail it just acted on. So the read ranks within each UID and mutation rather than across the answer.

Five is the recent history of one value. A reading is settled against the newest store of that value which asked for what the server now reports, and the stores behind it are the ones a convergence pass abandoned or a later call superseded — a caller-authored requester is per invocation, so an agent that stars and unstars one message leaves a record per call and nothing deletes one. A value whose newest five stores all fail to explain the reading is a value somebody changed after MailFathom last wrote it, which is the answer the older stores would have produced anyway. Reaching the number therefore means one occurrence carries more unspent stores of a single value than any attribution has a use for, and the adapter says so in a log line rather than truncating in silence.