Wez Furlong
c2444b6266
add expiry to per-msg scheduling overrides
...
This commit allows setting a per-message `expires` timestamp
via msg:set_scheduling (and thus msg:import_scheduling_header).
The expiration takes precedence over max_age; max_age will be
ignored for messages that have configured and expiration time.
The expiration time is independent of the other scheduling
restrictions.
2025-03-15 07:18:13 -07:00
..
2023-02-25 20:41:50 -07:00
2024-11-12 12:28:40 -07:00
2023-02-26 15:01:05 -07:00
2024-06-10 09:30:17 -07:00
2024-06-10 09:30:17 -07:00
2023-11-29 12:08:34 -07:00
2023-02-25 20:41:50 -07:00
2023-11-29 12:08:34 -07:00
2023-03-14 18:53:47 -07:00
2023-03-14 18:53:47 -07:00
2023-02-26 15:01:05 -07:00
2023-02-26 15:01:05 -07:00
2024-03-31 06:57:59 -07:00
2023-02-26 15:01:05 -07:00
2024-01-05 15:31:05 -05:00
2023-02-25 20:41:50 -07:00
2025-03-15 07:18:13 -07:00
2025-02-07 06:13:14 -07:00
2024-06-10 09:30:17 -07:00
2023-03-02 14:46:30 -07:00
2023-02-26 15:01:05 -07:00
2024-06-10 09:30:17 -07:00
2023-02-25 20:41:50 -07:00
2023-08-25 08:38:09 -07:00
2023-06-30 05:20:35 +00:00
2023-05-08 17:37:54 -07:00
2023-02-25 20:41:50 -07:00
2024-06-10 09:30:17 -07:00
2024-06-10 09:30:17 -07:00
2023-05-08 17:37:54 -07:00
2024-01-05 15:31:05 -05:00
2023-08-25 08:38:09 -07:00
2025-03-15 07:18:13 -07:00
2023-08-25 08:38:09 -07:00
2025-02-19 15:55:12 -07:00
2025-02-19 15:55:12 -07:00
2023-03-14 18:53:47 -07:00