Configuring Speed‑Aware Cache TTL for Railway Train Position Updates
The goal is to guarantee that the age of cached train‑position data never exceeds a distance‑based staleness limit derived from current speed, block length, and required reaction time, ensuring downstream signaling decisions rely on sufficiently fresh information. Presently the cache uses a fixed 30‑second TTL with no documented mechanism to vary this timeou