Directories
¶
| Path | Synopsis |
|---|---|
|
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.
|
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. |
|
Package redis provides a Redis- or Valkey-backed gateway.Outbox, so a connection's unacknowledged tail survives a node failure: a client that reconnects to a different process still finds the messages the original process had sent but not yet had acknowledged, and they are redelivered.
|
Package redis provides a Redis- or Valkey-backed gateway.Outbox, so a connection's unacknowledged tail survives a node failure: a client that reconnects to a different process still finds the messages the original process had sent but not yet had acknowledged, and they are redelivered. |
Click to show internal directories.
Click to hide internal directories.