diff options
| author | Thomas <31560900+0xtlt@users.noreply.github.com> | 2022-12-15 19:58:40 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-12-15 19:58:40 +0100 |
| commit | 0d93f3033ecdc7dd0fe7ff1d5082156fe0d06aa0 (patch) | |
| tree | 87e4c44571218f1eb743d742308f8a95816ab7e8 | |
| parent | 8d3f5c6e79cc25a59e8148b6a98c1cac8f960159 (diff) | |
Update 40.md
Co-authored-by: Semisol <45574030+Semisol@users.noreply.github.com>
| -rw-r--r-- | 40.md | 6 |
1 files changed, 4 insertions, 2 deletions
| @@ -43,8 +43,10 @@ Clients SHOULD ignore events that have expired. | |||
| 43 | Relay Behavior | 43 | Relay Behavior |
| 44 | -------------- | 44 | -------------- |
| 45 | 45 | ||
| 46 | Relays SHOULD NOT delete an expired message immediately on expiration. Relays that wish to purge expired messages from their DB should allow for a grace period before deletion. For example, this could be 24h after event expiration. | 46 | Relays MAY NOT delete an expired message immediately on expiration and MAY persist them indefinitely. |
| 47 | Relays MAY choose to not delete expired messages. | 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. | ||
| 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. | ||
| 48 | 50 | ||
| 49 | Suggested Use Cases | 51 | Suggested Use Cases |
| 50 | ------------------- | 52 | ------------------- |