Table of Contents

Interface IOutboxStoreCapabilities

Namespace
Excalibur.Dispatch
Assembly
Excalibur.Dispatch.Abstractions.dll

Reports data-shaped capabilities of an IOutboxStore that a conformance/behaviour check must know to assert the correct contract, rather than assuming one uniform storage model.

public interface IOutboxStoreCapabilities
Extension Methods

Remarks

Outbox stores fall into two storage models for a successfully-sent message. Tracking stores retain the row and transition it to a terminal Sent state (a status column), so a sent message remains countable and cleanup-eligible. Delete-on-sent stores (the relational Postgres and Oracle providers) delete the row the instant it is marked sent — there is no sent row to count, and cleanup is a no-op because the row is already gone.

This is a data-shaped capability in the BCL idiom (Stream.CanSeek, HttpClientHandler.SupportsAutomaticDecompression, and the sibling IInboxStoreCapabilities) — a property intrinsic to the store, not a separately-registered marker and not an inheritance-buried virtual. A store that does not implement this interface is treated as a tracking store (the default), so only delete-on-sent stores need declare it.

Properties

SupportsSentTracking

Gets a value indicating whether the store retains a successfully-sent message as a countable, cleanup-eligible Sent row.

bool SupportsSentTracking { get; }

Property Value

bool

true for a tracking store that keeps the sent row (statistics count it and cleanup removes it); false for a delete-on-sent store that removes the row on mark-sent (no sent row to count, cleanup is a no-op).