conformance

Overview ¶

Package conformance is a shared test suite every gateway.Outbox implementation must pass, so gateway.MemoryOutbox and persistence/redis.Outbox (and any third-party implementation) are held to the exact same at-least-once contract: a message is retained once appended, stamped with a per-connection id and sequence the Outbox itself mints in append order, remains readable until acknowledged, is redeliverable in Seq order, disappears only on Ack or DropConn, and rejects an Ack whose generation trails one already accepted for the same connection. An implementation that drops an unacknowledged message early would silently lose the tail a reconnecting client depends on; one that let two messages share a Seq would let a Seq-deduping client silently discard one; one that accepted a stale-generation Ack would let a node already fenced out by an owner-lease takeover (see gateway.WithOwnerLease) keep draining the tail out from under its successor.