On Thu, 2013-05-16 at 13:50 +0200, Milan Crha wrote:
> testing libical 1.0, I noticed that when saving an event with a
> timezone, its whole daylight saving time change history is saved with
> the event, which might be fine with respect of correctness, but also
> includes useless information, like in my case, where the first timezone
> part begins at 1949 and ends at 2037, while I entered the event today,
> in 2013, with one instance only.
Hrm, I just realized that it also breaks interoperability (in some
I save an event, through CalDAV, to:
- a Google calendar, it returns event with only timezone for 1970
(while I saved it with whole history);
- a Zimbra server, it returns event with only the last timezone record,
which is for 2037 (remember, my event is for 2013);
- a DAViCal server, it returns event in a complete form, as I wrote it.
While DAViCal does the most correct thing, it's still wrong with respect
of network usage (not caused by DAViCal), because the CalDAV stores
timezones for each single component, thus it means 12KB more data per
each event stored in a calendar being transferred from (or to) the
server. With absolutely no gain. Count with 1000 items in a calendar and
you get 13MB download, instead of 1MB.