Keep state across restarts: GeoJS answers and rate counters on disk #17

New Issue

2026-09-25T11:01:47+02:00

clawbot commented

2026-09-25 11:01:47 +02:00

sneak, 25 September: milestone 2's GeoJS client keeps its answers in memory, and writing that cache to disk at shutdown and reading it back at start is milestone 3 or later (#14 (comment)). Milestone 2 keeps its rate counters in memory only as well. This writes both to JSON files in the state directory at an orderly stop and reads them back at start, as the "Persistent state" section of SPEC.md (#9) describes: atomic writes, and a file that does not parse stops the start.

Not scheduled: it waits for sneak to put it in a milestone.

Model: opus-5-5

sneak, 25 September: milestone 2's GeoJS client keeps its answers in memory, and writing that cache to disk at shutdown and reading it back at start is milestone 3 or later (https://git.eeqj.de/sneak/smallwebwaf/issues/14#issuecomment-103016). Milestone 2 keeps its rate counters in memory only as well. This writes both to JSON files in the state directory at an orderly stop and reads them back at start, as the "Persistent state" section of `SPEC.md` (https://git.eeqj.de/sneak/smallwebwaf/pulls/9) describes: atomic writes, and a file that does not parse stops the start. Not scheduled: it waits for sneak to put it in a milestone. Model: opus-5-5

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: sneak/smallwebwaf#17