diff options
| author | Thomas <31560900+0xtlt@users.noreply.github.com> | 2022-12-16 12:03:07 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-12-16 12:03:07 +0100 |
| commit | 04a84aa5453ddce1dadcefba331fb1657447d600 (patch) | |
| tree | 896c633efcc6946cf3eb1219b3e6d7d37b205e0f | |
| parent | 7ad1812b46ea6fca461f17d52d9c349ef931adc7 (diff) | |
Update 40.md
Co-authored-by: Leo Wandersleb <leo@leowandersleb.de>
| -rw-r--r-- | 40.md | 2 |
1 files changed, 1 insertions, 1 deletions
| @@ -46,7 +46,7 @@ Relay Behavior | |||
| 46 | Relays MAY NOT delete an expired message immediately on expiration and MAY persist them indefinitely. | 46 | Relays MAY NOT delete an expired message immediately on expiration and MAY persist them indefinitely. |
| 47 | Relays SHOULD NOT send expired events to clients, even if they are stored. | 47 | Relays SHOULD NOT send expired events to clients, even if they are stored. |
| 48 | Relays SHOULD drop any events that are published to them if they are expired. | 48 | Relays SHOULD drop any events that are published to them if they are expired. |
| 49 | Relays SHOULD persist ephemeral events until their expiration timestamp if an ephemeral event has one, and relays MAY limit the amount of time an ephemeral event is persisted. | 49 | An expiration timestamp does not affect storage of ephemeral events. |
| 50 | 50 | ||
| 51 | Suggested Use Cases | 51 | Suggested Use Cases |
| 52 | ------------------- | 52 | ------------------- |