Confirmed users
503
edits
Calendar Talk:Feature Implementations:Calendar Cache: Difference between revisions
Jump to navigation
Jump to search
Calendar Talk:Feature Implementations:Calendar Cache (view source)
Revision as of 19:49, 28 December 2006
, 28 December 2006no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
offline (so not caching!) | offline (so not caching!) | ||
| Line 24: | Line 22: | ||
can do this. If there is no real file (like wcap, caldav), they could download | can do this. If there is no real file (like wcap, caldav), they could download | ||
into a storage calendar. It should still work when only part of the remote | into a storage calendar. It should still work when only part of the remote | ||
calendar is downloaded, because the local | calendar is downloaded, because the local storage is not used for anything | ||
except showing items when offline. | |||
There is some caching possible with this: When a provider supports downloading | |||
the entire file, queries can be done on the local copy. (this is currently | |||
already how ics calendar work, with a memory provider as local copy) | |||