Originally Posted by
MostlyAir
The fare calendar reads from a cached source. So if the fares change it takes somebody else searching for that fare to change it in the calendar.
Aw jeez, seriously? Of course you need caching on a data set that large but what kind of Micky-Mouse school of programming did their developers go to that they'd rely on user actions to rebuild the data piece-by-piece? At least flush the cache when new fares are loaded or set it to rebuild automatically every 5 minutes... as someone involved in web dev myself I'd be embarrassed to turn out a product with such a glaring deficiency.