ConsumeChecks class

The two stateful §7.2 checks: the freshness bound over issuedAt / expiresAt, and the duplicate-execution record of item 11.

They travel together because the spec ties them together. §7.2 (Bounding the record) makes the acceptance window and the record's retention the same bound. Passing them as one argument is what stops a deployment configuring a five-minute record and an unbounded acceptance window, which reads as a working replay defence and is not one.

Like PayloadPolicy, this is a required argument. Whether the task a consumer implements is consequential (§2) is a decision only that consumer can make, and the failure mode of getting it wrong silently — an ACL grant applied twice by a mediator retry — is not one to discover after the fact.

Constructors

ConsumeChecks({required FreshnessPolicy freshness, required ReplayPolicy replay})
const

Properties

freshness → FreshnessPolicy
Bounds the document in time (SPEC §4.2, §7.2 item 4).
final
hashCode → int
The hash code for this object.
no setterinherited
replay → ReplayPolicy
Applies (or knowingly disapplies) SPEC §7.2 item 11.
final
runtimeType → Type
A representation of the runtime type of the object.
no setterinherited

Methods

noSuchMethod(Invocation invocation) → dynamic
Invoked when a nonexistent method or property is accessed.
inherited
toString() → String
A string representation of this object.
inherited

Operators

operator ==(Object other) → bool
The equality operator.
inherited