Confirmed users
503
edits
Calendar:Cache: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 66: | Line 66: | ||
change, it can build a changelist and immidiatly remove the non-changed | change, it can build a changelist and immidiatly remove the non-changed | ||
events from memory. | events from memory. | ||
= Implementation = | |||
The cache is stored as a storage calendar. | |||
storage calendar needs an option to return a different type and uri. (the uri should not point to the cache file, but to the real file) | |||
The auth calendar (ics) can return a list of changes since the last flush. The calendar can flush the current data while checking if the file didn't change since last getUpdates. | |||
And observer watches for changes to the cache calendar, and builds a changelog. | |||
On a timer, this changelog is checked with the changelog from the auth calendar for conflicts. Then the two changelogs are applied to the 'other' calendar. | |||