Handle day-specific requests accounting time zones

[dbonino]

Currently the back-end retrieves "onset" data for a given day based on a day information specified as a LocalDate. This is likely to generate errors for all users having a device working in a timezone different from the one of the server. In fact, the method public List<Exposee> getSortedExposedForDay(LocalDate day) is not timezone aware and therefore is prone to timezone related errors. (As reported in official Javadocs This class does not store or represent a time or time-zone. Instead, it is a description of the date, as used for birthdays. It cannot represent an instant on the time-line without additional information such as an offset or time-zone.

E.g., if the timezone of my device is set to UTC for whatever reason, the request sent by the device will contain a day specification, which is implicitly referred to the device timezone. However, as it is interpreted as "local" datetime on the server, the result will consider an interval which is shifted by 1 hour (or 2, depending on the daylight saving period).

This might introduce errors in notifications to users.

[dcremonini]

Just for keeping the content of your post current, the onSet field of type String was recently renamed keyDate and its type was changed to long. I agree that managing the timezone someway is very important.

[slyfer]

The get exposed parameter is a Date (first string now a long (epoch millis)) sono timezone is not relevant.