Confirmed users
503
edits
Calendar:Cache: Difference between revisions
Jump to navigation
Jump to search
m
→Implementation
No edit summary |
m (→Implementation) |
||
| Line 73: | Line 73: | ||
Two models are possible: | 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. | 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. | ||