3 ms·
I wish we had something like this on my last project. On my last project, there were two separate systems for determining the local Timestamp. One of them was
by stcredzero 16y ago
I wish we had something like this on my last project. On my last project, there were two separate systems for determining the local Timestamp. One of them was based on the time from the local machine's clock. The other took time from a central mainframe/transaction processing system. (Call these system-A and system-B) We really could've used something like the article proposes for both systems.
Here's the thing: The application would calculate the timezone based on system-A, then use the time from system-B to do a lookup into a GMT-based table using system-B's time. All well and good, until the testers tried to test calling outside allowed hours by changing their local system clocks. This mess resulted in trying to look up entries in the table for timezones the middle of the Pacific. Boom!
The worst part? Trying to explain to the testers how this was an inherent flaw in the legacy system and not a result of the upgrade. (Yes, I would've changed it if I were allowed to.)