Enum StorageCapabilities

Namespace

Millrace.Storage

Assembly

Millrace.dll

Optional powers a provider advertises; the engine adapts (ARCHITECTURE.md §4 P3). Batch claiming is not a capability — MaxCount is always honored best-effort (returning fewer jobs than requested is always conformant).

[Flags]
public enum StorageCapabilities

Fields

None = 0

No optional powers.

Not a deficiency: a provider advertising None is fully conformant and loses no guarantee. The engine simply falls back — adaptive polling instead of pushed wakeups — so the difference is latency, never correctness.

Notifications = 1

The provider implements IStorageNotifier and pushes queue wakeups (e.g. Postgres LISTEN/NOTIFY). Without it workers use adaptive polling. Notifications are a best-effort latency hint — correctness never depends on them.