On Wed, 2009-01-07 at 16:05 +0100, Milan Crha wrote:
> On Wed, 2009-01-07 at 12:45 +0100, Patrick Ohly wrote:
> > ...
> > The plan for change tracking is to get rid of the dependency on
> > e_book_get_changes(). I already stopped using e_cal_get_changes()
> > because it was too inflexible. Instead I'll rely on the REV resp.
> > LAST-MODIFIED properties: the backend must update these each time an
> > item is modified. This seems to be supported by most backends. Are there
> > backends which are known to not support this?
> I'm not sure how much related, but just in case: there are some backends
> not storing the LAST-MODIFIED in UTC, as is described in:
> http://bugzilla.gnome.org/show_bug.cgi?id=360813

Thanks for pointing that out. Luckily it is irrelevant for change
tracking because the client won't try to interpret the values as time.
It will also work when an item changes from local time to UTC (after
applying your patches) because the string will be different.

Bye, Patrick Ohly

Evolution-hackers mailing list

Reply via email to