I have been studying several topics that address the question of the vigency of Daylight Saving Time [DST] by calling certain Clock Properties
and how it can positively or negatively interfere with the results of some operations.
But what I don't finish understanding is how 'Instant'
decides this information.
Since there is no Clock Property
that references a particular city or place that can be programmatically defined -and 'Instant'
always knows accurately the Time zone and an eventual DST- I estimate that this information about the Time zone and DSTs take as reference internal time settings manually defined by the User on the Android device or from Sensor... but I am not very clear how this happens.
The Time zones are divided by bands »
But not necessarily an entire Time zone band adopts DST evenly throughout the whole track. According to individual provisions, there will be countries within this range that adopt the DST - starting and ending on different days and hours- and there will be countries (or States) that do not adopt it.
This means that so that 'Instant'
can elucidate DST validity, somehow it is taking from device not only the reference of the Timezone defined, but also the place of the device... which means the same 'Instant'
defined programmatically will have different results according to the Timezone and the Location of the User.... and even more: the vigency or not of DST will be specifically linked to this Location!
My questions are:
-
Where do
'Instant'
get the current Timezone? Is this done based on the device location sensor and later calculated? Or such information comes from UI? -
Where did
'Instant'
get the User Location? Is this done by the device location sensor? Or such information comes from UI? -
To decide DST vigency, does
AI2
use any specific API or any specific NTP Server [Network Time Protocol]? -
If so, what would be this API or this NTP Server?
TYA
Lito @>-->---