264
edits
Calendar:Feature Implementations:Calendar Cache: Difference between revisions
Calendar:Feature Implementations:Calendar Cache (view source)
Revision as of 22:56, 16 November 2006
, 16 November 2006no edit summary
XFallenAngel (talk | contribs) (Initial Version) |
XFallenAngel (talk | contribs) mNo edit summary |
||
| Line 7: | Line 7: | ||
This page describes what is needed to create an abstract implementation to cache calendar events in general. This can be a subset of events or the whole calendar. The latter is needed for offline support. Caching in general will speed up access to remote calendars. It must however be optional, since i.e the memory calendar should not need to be cached. | This page describes what is needed to create an abstract implementation to cache calendar events in general. This can be a subset of events or the whole calendar. The latter is needed for offline support. Caching in general will speed up access to remote calendars. It must however be optional, since i.e the memory calendar should not need to be cached. | ||
Note also that as of now, this is only a collection of thoughts. | Note also that as of now, this is only a collection of thoughts. Also, this also applies to tasks. Only writing events instead of tasks and events was used to optimize readablity. | ||
===The Problem=== | ===The Problem=== | ||
| Line 40: | Line 40: | ||
===Syncronization Issues=== | ===Syncronization Issues=== | ||
It is always possible that the cached | It is always possible that the cached events are not up to date. In this case those events need to be resyncronized with the server. Depending on the current action, the impact of these issues are differently severe. Additional UI is definativly needed to handle conflicts. | ||
====Displaying Events==== | ====Displaying Events==== | ||