Quote:
Originally Posted by Ed Hansberry
Not odd at all. If you don't apply the patch, you will only be affected if you live in, visit or exchange meeting requests with people in the 13 areas addressed by the patch.
|
What needs to be understood is that within the OS somewhere (used to be in the registry) is a table that assignes DST start and stop times for various places. By places I mean distinct TimeZones and local variants. For example, while Arizona is in the US Mountain Time Zone, they, as a State, don't subscribe to DST at all, so you have to have a different set of entries than you would for Colorado, even though they are both GMT -7.
As places change when they do what, you have to fix what the table says to accurately reflect the reality where individuals live. A lot of the issues came a few years back when the whole world seemed bent on changing when they started and stopped DST, and natuarally all had their own ideas of when that should be and when the change should start. For each change a new set of rules needs to be applied. With the way MS does it now, all the rules are replaced, even if most just stay the same.
I gave some thought the old way in the registry, where you could go make the change to your life individually, but I would guess that would cause some issues when some folks would/could fix stuff and others didn't. You'd wind up with the errors in time translation, between 'patched' and 'unpatched' individuals. So, until DST start and stop times are universally implemented, we will always have this issue, unless we just kill it altogether...universally.
P.S. with the advent of converged devices, you also add the complexity of how well the carrier keeps track of what they send to the device in the way of time and TZ.