Make the iCal feed cache-first with data-version awareness #62

New issue

Open

opened 2026-07-01 01:06:34 +00:00 by manlycucumber · 0 comments

manlycucumber commented

2026-07-01 01:06:34 +00:00

(Migrated from github.com)

Problem

The feed can be requested often by polling calendar clients; it must be cacheable and honour the data-version so corrections propagate without per-request engine work.

Acceptance criteria

Feed responses are cached and carry appropriate cache headers and an ETag.
A data-version bump invalidates the cached feed.
Conditional requests return 304 when unchanged.
Generating the feed for a full year does not exceed reasonable memory/time limits.

Notes

Reuse the transient/data-version machinery from v0.2.0.

## Problem The feed can be requested often by polling calendar clients; it must be cacheable and honour the data-version so corrections propagate without per-request engine work. ## Acceptance criteria - [ ] Feed responses are cached and carry appropriate cache headers and an ETag. - [ ] A data-version bump invalidates the cached feed. - [ ] Conditional requests return 304 when unchanged. - [ ] Generating the feed for a full year does not exceed reasonable memory/time limits. ## Notes Reuse the transient/data-version machinery from v0.2.0.

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/Ordo#62

No description provided.

Rows
Columns