Compute cold dates dynamically with cache-friendly headers #16

Closed
opened 2026-07-01 00:57:54 +00:00 by manlycucumber · 1 comment
manlycucumber commented 2026-07-01 00:57:54 +00:00 (Migrated from github.com)

Problem

Dates outside the pre-generated hot set must still be answerable. A dynamic endpoint computes them via Core on demand and emits headers that let Cloudflare cache the result immutably.

Acceptance criteria

  • Cold (date, system, calendar) requests are computed via Core and returned in the canonical envelope.
  • Responses set long immutable cache-control and a stable cache key per the input tuple.
  • A repeated cold request is served from cache rather than recomputed.
  • The dynamic path is covered by tests for a never-pre-generated date.

Notes

Responses are immutable per key; only a data-version bump should invalidate them.

## Problem Dates outside the pre-generated hot set must still be answerable. A dynamic endpoint computes them via Core on demand and emits headers that let Cloudflare cache the result immutably. ## Acceptance criteria - [ ] Cold (date, system, calendar) requests are computed via Core and returned in the canonical envelope. - [ ] Responses set long immutable cache-control and a stable cache key per the input tuple. - [ ] A repeated cold request is served from cache rather than recomputed. - [ ] The dynamic path is covered by tests for a never-pre-generated date. ## Notes Responses are immutable per key; only a data-version bump should invalidate them.
manlycucumber commented 2026-07-03 05:50:37 +00:00 (Migrated from github.com)

Delivered in #135 (squash-merged to develop).

Delivered in #135 (squash-merged to `develop`).
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Directorium/Api#16
No description provided.