Feed engine logging, npoints meta data separation for increased robustness and improved timezone support
Meta data npoints
The number of datapoints in a feed was stored in one meta data file along with other meta such as the feed start time and feed interval. In the event of a system crash mid write to a meta file there is a risk that several of these meta properties can get corrupted. Its only the npoints property that needs to be updated regularly the feeds start time and interval only gets written to once at feed creation. By separating the meta data that gets written at the start and the meta data that gets written to regularly into two different files we reduce the risk of corruption as npoints can be read independently and corrected from file size divided by 4 bytes per datapoint while start time and interval are harder to recover from if you dont have a backup.
Improved timezone support
Daily data types now use the PHPTimeSeries engine and support a midnight reset time set by the user timezone setting under user account. This is a significant change as there was previously minimal support for different timezones if the system time was different from the user timezone.