Confirmed users
503
edits
Calendar:Cache: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 69: | Line 69: | ||
= Implementation = | = Implementation = | ||
The cached data is stored in a storage calendar. The cache engine is a wrapper around the storage. | |||
Two models are possible: | |||
- The storage represents the last known state of the autorative calendar, and changes made by the user are queued | |||
- The storage represents what the user sees, and changes are directly propagated. | |||
The second model makes querying much easier, so that is choosen to be really used. In this model the cache needs to keep a list of items as they weere before the user changed them, so as they are in the autorative store. This is needed for conflict detection and resolution. | |||
== More technical details == | |||
The cache is stored as a storage calendar. | The cache is stored as a storage calendar. | ||